Allow Entry Of "Overridden" Costs/Fill, Cost/Gal.?
I like the improvements which you folks have made over the past year or so. But I take exception to the way that some rounding "distorts" amounts!
For example, I always take the fill up to the nearest nickel (5 US cents), and leave no pennies out there! Yet on my last fill on your site, instead of $21.00, as shown on my receipt for 9.549 gallons of gas at $2.119/gallon, you're showing 20.998! On the Windows calculator, $20.998251 is computed, indicating that you're rounding to the nearest tenth of a cent, where you should be rounding to the nearest cent. Or better yet, put a check-box next to the amount that allows the user to override the computed cost (within a certain margin) to put the EXACT amount spent without re-computing it! (Same with price/gallon--it shouldn't recalculate if I enter my exact cost of the fill.) Theoretically, I shouldn't see any pennies in any of my averages, and so my Systems Analyst mind does "WTF?"s every time I see that stuff! Hopefully this makes "cents!" (Or won't, in the case of my averages! :coolsmiley: ) |
Something to keep in mind is that fuel pumps may not be rounding up half the time, but two thirds of the time. They don't follow the accepted rounding rules that everything else does.
|
Where are you seeing those calculations?
Looking at your log, I see your "$21.00"- Accord Touring Fuel-up Log | Fuelly |
Quote:
Also, when I go in to edit my most recent entry, the amount shows 20.998. That's what I'm talking about--on the gas receipt, I enter the miles from my tripmeter(s) before I reset them, and the price/gallon, gallons dispensed, and total cost is printed on the receipt. (I also note the time since last fill, as well as the average mph to calculate city/highway spread, which is on my car's trip computer, and which resets with the tripmeter(s).) I should be able to enter those values without any computations being done in the page code if I wish, and have my averages and stats computed from those "raw" numbers I enter. Hope that clarifies things! :) |
Thanks for the specific examples. I'll pass it along to our Team for review to see if/how we can best implement a "fix".
|
Please take a look now. This should be resolved. Never should've been calculating to the third decimal place. Sorry about that!
|
Sorry for the late reply--PERFECT!
Thanks for the fix! :D |
All times are GMT -8. The time now is 09:24 PM. |
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2024, vBulletin Solutions, Inc.