> Will Google change the example code to work out of the box someday? It's the > most ridiculous thing I have ever seen on this guys.
Why should they? Google require the developer to declare whether they're using a sensor or not, the developer has to make a concious choice in this, its not something to be defaulted. It's not difficult after all, but some people just don't bother reading what they're using. When the ones that turn up here have run into the problem, they haven't even bothered looking down the page here to see if anyone else has had the same problem!! The only people hitting this issue are the ones that don't care enough to check into what they're doing, not even after they've had an error report. My guess is the majority of people don't have a problem with it at all. It WOULD be nice if the error message was more explicit - perhaps it will be when the sensor parameter is made mandatory. 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 -~----------~----~----~----~------~----~------~--~---
