> Those few cases are advanced pages and developers of those do not > report key problems. It would be better that key signup page code > would give sensor=false. Those who make real time gps tracking pages, > do read the documentation and will find an announcement about sensor > parameter.
It may be that Google's intention is to FORCE the user into making a conscious choice about this parameter, by deliberately NOT putting something useable in the example that's likely to be copy pasted. Kind of like a declaration "I have read the terms ..." etc. However, its pretty clear now that copy-pasters are not recognising true_or_false as something they need to do anything about. Maybe sensor=XXXXX_CHANGE_THIS_PARAM_XXXXX or something would be more obvious cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
