On Wed, Jan 4, 2012 at 8:59 AM, Adam Stroud <[email protected]> wrote:
> My knee-jerk reaction was that a value of "true" would suffice for my
> case, I was just interested in how others interpreted the javadoc.
Strictly my opinion.
1 - They don't define "route" or "path", just use a very broad description
("any kind of route information") and give one example.
2 - The javadoc references the TOS, then has a TODO to show the link which
has never been updated - so apparently they don't care that much about
referencing the TOS and having developers adhere to it.
3 - The only reference to "route" in the TOS is to real-time navigation or
"enterprise" applications (8.7) so if your app is neither, it can be argued
that you don't need to do anything.
4 - The Maps library is essentially abandoned.
5 - I'd bet money that 99% of all apps that have a map return false (the
default and what is shown in the MapView tutorial) and have never looked
back, if for no other reason than carelessness.
Given these points, IMO, it is irrelevant what you return. I'm not saying
you should ignore it on purpose, but you probably have better things to
work on then implementing this function to be absolutely correct.
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
