google-code-export / geobeagle

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

Error when trying to show edited coordinates on map #68

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Add a geocache from geocaching.com
2. Edit the coordinates (i changed both longitude and latitude)
3. Try to plot the new location on the map.

What is the expected output? What do you see instead?
Expected output would be to see the new location on the map, instead an
error appears: "Error: android.text.SpannableString"

What version of the product are you using? On what operating system?
The version of Geobeagle available from Android Market (10th of August,
2009) on Android version 1.5.

Please provide any additional information below.

Original issue reported on code.google.com by junkbo...@gmail.com on 12 Aug 2009 at 8:12

GoogleCodeExporter commented 9 years ago
I have tried this and it works for me. Did you enter an invalid coordinate 
format?

Original comment by andpet@gmail.com on 9 Sep 2009 at 9:02

GoogleCodeExporter commented 9 years ago
if so, what is the correct coordinate format? :)

Original comment by junkbo...@gmail.com on 15 Sep 2009 at 10:51

GoogleCodeExporter commented 9 years ago
The coordinate format is:
(Latitude) xx xx.xxx
(Longitude) xx xx.xxx
What coordinates did you enter which weren't accepted?

Original comment by andpet@gmail.com on 16 Sep 2009 at 10:43

GoogleCodeExporter commented 9 years ago
I am not sure what did it, but I can't seem to reproduce the error with the 
newest
version, the error basically appeared everytime I had a multicache, I used 
geobeagle
to "Search online", downloaded location data for a cache with the Google Maps 
link,
figured out the first part of the cache, edited the cache coordinates to 
indicate the
location of the second waypoint, and then it would throw that error about 
spannable
string at me. I think I used the same coordinate format. It was steadily 
reproducable
before, but now I can't seem to make it happen even once (version 0.99)...

Original comment by junkbo...@gmail.com on 24 Sep 2009 at 10:02

GoogleCodeExporter commented 9 years ago
Even if the problem is not apparent, we need to make sure we handle erroneously 
formatted coordinates.

Original comment by andpet@gmail.com on 24 Sep 2009 at 8:34

GoogleCodeExporter commented 9 years ago

Original comment by stephen5...@gmail.com on 9 Sep 2010 at 2:49