search

joelmap / geohashdroid

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

Wrong reticule #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Point your time machine at August 17, 2012
2. Teletransport at 45.686N 9.839E
3. Go!

What is the expected output?  What happened instead?
It rounds me up in the 45-10 graticule instead of 45-9,
"meetupping" me at 45.973N 10.143E instead of 45.973N, 9.143E
This only happens when I check the "use closest",
if i put the graticule by hand it works.
It event works if I pick my location from the map.

What version of Geohash Droid are you using?  On what phone?
0.7.17 on Samsung Galaxy S3 (GT-I9300)

What version of Android is running on that phone, if you know?
Android 4.0.4

Original issue reported on code.google.com by camillo....@gmail.com on 16 Aug 2012 at 10:57

GoogleCodeExporter commented 9 years ago 
It sounds like that's just a minor misunderstanding.  The "Use Closest" option 
is for whatever point is the closest at that moment, not necessarily the 
graticule you're standing in.  Meaning, the hashpoint at 45N 10E was closer to 
45.686N 9.839E than the 45N 9E one was, so it picked that one.

If you want a specific graticule, you'll need to enter it by hand (or use the 
map interface).  But "Use Closest" is for whatever point is closest.  That 
might be a bit confusing because I couldn't think of a better phrase to use, 
given the space restrictions on phone screens.  Sorry about that.

Original comment by captains...@gmail.com on 17 Aug 2012 at 3:48

GoogleCodeExporter commented 9 years ago 
Ouh, I see. It points me to the nearest meetup, not the "nearest" graticule.
Fine! Sorry for opening an annoying issue :)

Original comment by camillo....@gmail.com on 18 Aug 2012 at 12:33