I'll have it user settable... IF the threading idea falls through for whatever reason. If i can have the file IO done separate from the actual distance calculation it should work out great. Only problem would be if RR is closed between writes. RR really needs a way to let plugins know its terminating.
Originally Posted by GizmoQ
Originally Posted by JohnWPB
I've got a kick out for floating coordinates that monitors the heading value. This should work really well... unless you guys are out doing high speed donuts lol.
For a quick trip to the store, many of us do not have the computer come on, but would like to keep the "system odometer" in sync with those lost tracked miles ect. Also the "floating" of the lat and lon can add up pretty fast. Back when I was trying to get Festy's gas mileage thing to work, I noticed this. With the USB GPS puck here on the desk, I left it running for a day when I left in the middle of working on it and noticed that I had traveled a few miles hahah.
when i say the timer runs too fast at once per second only real issue is getting the lat and lon from RR before the CalculateDistance function is run. If RR hasnt reported back to the plugin before the function runs the result of the function is Nan and it crashes the system. I can probably easily write prevention for this.. but for now once every 2 seconds has been absolutely no issue on my 1.2ghz celeron i'm developing on.
As far as frequency of updates, personally I think once ever minute, 5 minutes or so is more than enough. Oil changes are the most frequent thing to change for example, & I doubt having to know within 2 seconds that's its time for an oil change is really going to matter that much :)
This would decrease the overall CPU usage, as well as not constantly thrashing / writing to the hard drive every 2 seconds.
I will definitely add it in some capacity as it is pretty easy to do. i was thinking more along the lines of having to calculate each time the oil change is done.
As for the cost per mile for items, that should be fairly simple to do. In your example its $17.50 for an oil change that is done every 3,000 miles:
$17.50 divided by 3000 = .006 cents per mile.
Will also incorporate this.
I also completely agree, and would love to see a fuel log wrapped into this! Fill er' up, enter the number of gallons, price per gallon and the odometer reading. At the next fill up do the same, and you can then have it calculate many miles per gallon you are getting.
One more thing i incorporated before leavin work on friday is a slider that gives you yet another visual indication of how close you are to exceeding your maintenance limit.