mattshobe / flightmap

Automatically exported from code.google.com/p/flightmap
Apache License 2.0
0 stars 0 forks source link

Map view switches between North Up and Track Up after returning from Tapcard Activity. #59

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Set your preferences to Track Up.
2. Click on an airport to go to the Tapcard Activity
3. Press the back button to return to the main map view.

What is the expected output? What do you see instead?
The map shows the correct track up view, then switches to north up and then 
switches back to track up. Each switch is about a second long (long enough to 
try to tap on an airport in each view).

Original issue reported on code.google.com by bonnieri...@google.com on 28 Aug 2010 at 3:02

GoogleCodeExporter commented 9 years ago
I can't reproduce this. I've been in and out of tapcard a bunch and have never 
seen it.

When you say "switches to north up" do you mean the same action that happens 
when you change the preference to north up? Specifically, when north up:
* The airplane icon moves to the exact center of the screen (instead of 3/4 
down when track up)
* The airplane icon is rotated to point at the current track (instead of 
pointing to the top of the screen when track up)

I suspect what actually happened is the GPS gave back a location with a missing 
bearing, which our code currently treats as being on a track of 0. In track-up 
view, that would mean the map would rotate to put north at the top of the 
screen. It may take a few seconds for the GPS to recover and give a track 
again, which would match the behavior you saw.

I think this is not a tapcard bug, but rather Issue 60 which I just filed. 
Closing out because I cannot reproduce it as described.

Original comment by ph...@google.com on 30 Aug 2010 at 4:38

GoogleCodeExporter commented 9 years ago
This is totally reproducible for me using the steps I described. Note that it 
doesn't reproduce on the emulator but only on the phone. I'll see if your fix 
for Issue 60 resolved it; what you described seemed to match what I'm seeing.
In the future please just assign back to me for more details if you're unable 
to reproduce.

Original comment by bonnieri...@google.com on 30 Aug 2010 at 5:16

GoogleCodeExporter commented 9 years ago
Issue 60 has been merged into this issue.

Original comment by bonnieri...@google.com on 30 Aug 2010 at 7:02

GoogleCodeExporter commented 9 years ago
It looks fixed. It can take a couple seconds to renew the GPS connection and 
update the map but it doesn't jump around anymore.

Original comment by bonnieri...@google.com on 30 Aug 2010 at 7:04