Y labels not visible on small screens such as x10 mini's

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Compare values shown in graph with those in screen that shows only numbers
2.
3.

What is the expected output? What do you see instead?
In previous version of MyTracks that was fine but now in screen that shows 
numbers under max. speed I have 70 km/h, but on graph screen it shows around 
60km/h.

What version of MyTracks are you using? On what version of Android? On what
phone?
1.1.1 Android 2.1 Huawei U8110

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by marko.ni...@gmail.com on 21 Feb 2011 at 4:23

[GoogleCodeExporter]

Can you send a screen shot?  It is not too uncommon to not be able see the 
absolute max speed if you only hit that a few times.

Original comment by sandordo...@google.com on 21 Feb 2011 at 4:42

[GoogleCodeExporter]

The thing is that problem appeared after update. I was looking at old tracks 
when I realized that graph is not showing correct values. In previous version 
(before update) it was ok, graph matched max speed values shown in "stats 
screen" (I don't know how to call it, not the graph screen, not the map screen 
but the third one).

Here is picture of graph screen...

Original comment by marko.ni...@gmail.com on 21 Feb 2011 at 6:12

Attachments:

• DSCF0903.JPG

[GoogleCodeExporter]

And here is related stats screen...

Original comment by marko.ni...@gmail.com on 21 Feb 2011 at 6:13

Attachments:

• DSCF0902.JPG

[GoogleCodeExporter]

On graph screen shot you can also see only partially shown numbers on X and Y 
axis, bug# 285.

Original comment by marko.ni...@gmail.com on 21 Feb 2011 at 6:15

[GoogleCodeExporter]

I for one cannot see the speed at all on your screen, so I don't know what is 
being displayed.

Original comment by sandordo...@google.com on 21 Feb 2011 at 6:24

• Changed title: Y labels not visible on small screens such as x10 mini's
• Added labels: Priority-High, Targeting-1-1, Work-Medium
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Sorry, I'm not sure I quite follow you. On first screenshot you can clearly see 
that numbers on both axis are half shown. On X axis numbers are cut on half, 
while on Y axis you can see elevation (altitude) numbers but left of them are 
numbers showing speed that are not full visible, instead you can see only 
second digit what is 0 (zero). Next to altitude 1,500 it is 0 value for speed, 
next to 1,750 is 20, 2,000 is 40 (km/h) etc. Hope this explanation will help.

I guess you changed title but this report wasn't about X or Y numbers cut off 
the screen, I made another report about that and it was merged with issue #285 
as it was duplicate. This report was about values in graph and stats that are 
not matching.

So as you can see my max speed in second screenshot is 66.60 but on graph max 
shown speed is below 60. And the same problem appears when previewing any track 
that I have saved in my phone. Before update I had no this problem.

Original comment by marko.ni...@gmail.com on 21 Feb 2011 at 8:02

[GoogleCodeExporter]

Assigning to bart since this is related to issue 285 which he is also assigned.

Original comment by rdama...@google.com on 30 Apr 2011 at 5:31

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by rdama...@google.com on 30 Apr 2011 at 5:44

• Added labels: Component-UI

[GoogleCodeExporter]

I just noticed this same issue. The real problem is when you have two graphs, 
like elevation and speed. With those two, the speed Y-axis numbers get pushed 
off screen.

Original comment by Jensen...@gmail.com on 19 Jun 2011 at 5:44

[GoogleCodeExporter]

Original comment by jshih@google.com on 9 Dec 2011 at 9:16

[GoogleCodeExporter]

Original comment by jshih@google.com on 26 May 2012 at 7:28

[GoogleCodeExporter]

Original comment by jshih@google.com on 2 Jun 2012 at 6:53

• Changed state: Fixed