Closed GoogleCodeExporter closed 9 years ago
If that happens, I'd suggest to support alternative external map apps as well.
I'm
thinking of andnav2 here.
Original comment by thomas.h...@gmail.com
on 15 Jan 2010 at 11:02
Hm. I'll have to look into that, really. There's most likely an Intent I can
send
which the stock Maps app would understand (and, if the alternative external map
apps
are designed to listen for it, they would, too). That wouldn't be too hard to
add,
if support for it exists. I'll look into it for 0.7.2.
Original comment by captains...@gmail.com
on 17 Jan 2010 at 4:47
Huh. That was actually pretty easy.
In SVN right now (r314), there's a feature on the main map (and soon to be in
the
Details screen) labeled "Send to Maps", accessed through the menu. That'll
send the
point out using the geo: scheme, which the Maps app will understand and plot.
Unfortunately, while the phone's Maps app seems to understand this sort of
scheme and
throw down an otherwise normal map point, I couldn't get it to get directions
to it
from where I lived. This might just be due to where I live (today's point puts
me in
the middle of nowhere and Google might not like navigating there), but you may
want
to test it against other points just in case.
Now, I don't know about andnav2, but if it's set up to listen for an Intent
with the
geo: scheme, it should prompt you as to which app you want to use when you send
it to
Maps. I'm hoping andnav2 supports it, because that IS sort of the standard way
of
doing things on Android, it appears, and if it aims to be a drop-in
replacement, it
should probably respond to it...
Original comment by captains...@gmail.com
on 17 Jan 2010 at 5:26
One small note: It appears that the way I'm sending the location to Maps, the
query
will attempt to pin it to the nearest address, if it can. For instance, with
my
nearest point today, the coordinates itself place it slightly off of a local
highway
road, but when sent to Maps, it pinned it at the nearest address ON the road.
It'll
get you in the rough area, but you'd still need to go back to GHD itself to get
more
specific. If it can't figure out an address for it at all (like when I was
testing
it yesterday and it put me in the middle of the abyss that IS central
Kentucky),
it'll pin it down to the actual coordinates, but then it can't do navigation.
Unfortunately, I can't work around this, since this is entirely in how the Maps
app
interprets the data I give it. The only other way I can send it to Maps will
simply
center the map on the point and not mark anything. Next time I make a
pre-release
(or if you're willing to brave the SVN repo), you can see if what I have is
what
you're looking for.
Original comment by captains...@gmail.com
on 18 Jan 2010 at 4:43
In version 0.7.2-pre1 (just uploaded now), I've got the Send To Maps feature
in. You
can get to it through the menu in either the main map or the details screen or
by
tapping the active final destination point (tapping an inactive one first
prompts you
to switch to that one, as it did before). The same caveats I mentioned above
still hold.
Please test it just so I know that's what you're looking for. Enjoy!
Original comment by captains...@gmail.com
on 24 Jan 2010 at 7:53
Thanks, the caveat is noted but it certainly adds usability. This means I can
get
transit/car/foot directions from afar and then switch to the Geohash app when I
get
close.
Original comment by ctros...@gmail.com
on 25 Jan 2010 at 6:29
Excellent. Then that'll be in 0.7.2 when it's released (as soon as I know the
new
layout stuff works on QVGA). Thanks!
Original comment by captains...@gmail.com
on 25 Jan 2010 at 7:57
Original issue reported on code.google.com by
ctros...@gmail.com
on 9 Jan 2010 at 11:39