search

energyplug / geobeagle

Automatically exported from code.google.com/p/geobeagle
0 stars 0 forks source link

Edited coords not saved after google mapping a route to the new coords #100

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
From the conversation
http://groups.google.com/group/geobeagle/browse_thread/thread/9b83d316fd239
9c4

What steps will reproduce the problem?
Ok so you are working on a multi and you have your next set of coords.
So, you press menu, touch edit, and input your new coords. Then you
touch save. Back on the main geobeagle screen you press menu, touch
google maps, touch the cache bubble, touch get directions. You travel
to the new location. You press back four times and you find that the
original coords have been restored.

1. "how do you recognize that the old values are back?"

Specifically the new values were 6.4 kilometers away from the original
values.

I navigated to the new coordinates. At that point is when I pressed
"back" four times to return to the main geobeagle screen. Surprisingly
I saw that according to geobeagle I was still 6.4 kilometers away. I
pressed menu -> edit and found that the original values were back. So
I really was 6.4 kilometers away... from the original coords.

I did several very seperated (meaning that each waypoint was multiple
kilometers from the previous waypoint) multis and observed the same
behavior every time.

2. Notice that I never get back to the edit screen by pressing back.
This is intended -- are your findings different?

Nope. I never get to the edit screen by pressing back either.

What version of the product are you using? On what operating system?
Geobeagle version 0.9.11 on stock OTA NON-Rooted 1.6 Doughnut on T-mobile 
G1.

Original issue reported on code.google.com by andpet@gmail.com on 28 Oct 2009 at 8:01

GoogleCodeExporter commented 8 years ago 
Same here running 0.9.14 on Cyanogenmod 4.2.3 ... I guess this is a problem 
caused by
the "stacking" done by Geobeagle ...

Original comment by Garry.M...@googlemail.com on 2 Nov 2009 at 7:29

GoogleCodeExporter commented 8 years ago

Original comment by stephen5...@gmail.com on 2 Nov 2009 at 7:39

GoogleCodeExporter commented 8 years ago 
Implementation note: It would be better to not supply the whole Geocache object 
as
part of intents. Instead, only send the id.
DbFrontend on andpet branch has code to read a single geocache from id.

Original comment by andpet@gmail.com on 4 Nov 2009 at 3:29

GoogleCodeExporter commented 8 years ago 
Issue 107 has been merged into this issue.

Original comment by stephen5...@gmail.com on 10 Nov 2009 at 5:32

GoogleCodeExporter commented 8 years ago

Original comment by stephen5...@gmail.com on 10 Nov 2009 at 5:32

GoogleCodeExporter commented 8 years ago 
 I encountered a problem today. I was doing a mystery cache where I had to change the coordinates. After saving 
the new cords, I used Google maps and the navigation feature to get me there. 
When I arrived, I exited the 
navigation and used the back button to return to the radar. Well at that point 
it show I was about a mile away. 
After going on a wild goose chase, I realized it had thrown out my new cords 
and reverted to the original cords. 
It did this twice both times I was sure to save the new cords. It always 
happened when exiting the navigation and 
using the back button to get back to the radar. I use a My Touch T-mobile 
phone. Thanks!
Dawn

Original comment by stephen5...@gmail.com on 12 Dec 2009 at 6:03

GoogleCodeExporter commented 8 years ago 
Hi,
Same Problem on my T-Mobile G1 not-Rooted, OTA V1.6, Beagle V.118?.
Oliver

Original comment by oliver.a...@gmail.com on 12 Dec 2009 at 9:44

GoogleCodeExporter commented 8 years ago 
Fixed (I think) in 1.0.2.

Original comment by stephen5...@gmail.com on 1 Feb 2010 at 5:28