Loading Profile...
Chart Improvement in y-Axis
I really [really!] love the chart improvement in 1.3. It is a huge win. However, I'd love to see a further improvement. I think this is a behavior I'm seeing since I imported 7 years of data into FatWatch. The issue is the y-scale. Right now it seems FatWatch is making a calculation of the range of the y-scale based on all data, not just the data in the current view. For example:
It would be really nice if the y-scale range were localized based only on the data in the current view, with some minimum so the chart doesn't look silly.
It would be really nice if the y-scale range were localized based only on the data in the current view, with some minimum so the chart doesn't look silly.
I’m wanting more
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Sorry, I didn't realize I had forgotten to reply to this.
Basically, I agree with you about the problem, but it seems that the only solutions would be:
1. enable pinch-to-zoom
2. change chart scrolling so that it moves a month at a time (like browsing through photos, for example) rather than continuously (as it does now).
I think #1 would be best, though I'm setting that aside to work on other features currently. #2 would be a dramatic change from the way things work now. Perhaps a double-tap could switch between continuous scrolling and month-by-month scrolling, but that might make things a bit too complicated.
At any rate, I will be doing something to resolve this, though it isn't at the top of my plate right now. -
Inappropriate?Thanks for the reply. I'm not sure why a 3rd solution isn't considered, simply dynamically calculate the min and max range based on the period of time shown in the view.
I'm going to make a guess that you are pre-rendering the entire image though, and that that is how the fling works so smoothly. Calculating the y-scale on the view would require regeneration of the chart.
You could do that recalc in a background thread, and "snap" the view after it is redrawn for the time period. This would give smooth scroll but would have the impact of possibly scrolling the chart out of the view.
Here is a current view of my chart. Sort of a bummer to not have the y-scale tighter, on the other hand it's further encouragement to keep moving the line down. :-)
Hopefully the other priorities you are working on are sharing weight history with friends via URL's. :-)
I’m having fun
EMPLOYEE
