On Apr 10, 9:29 pm, Rodrigo Díez Villamuera <[email protected]> wrote: > > - The error message is not explicit at all, it's erroneous. > - If hundreds of persons have the same problem you can do 2 things: Call > idiots to hundreds of people or think about you are doing something not so > well. > - Don't put a snippet of code in a <pre> tag, with a monospace font and the > your key inserted as a parameter if the code won't work at all.
See Issue 1092: http://code.google.com/p/gmaps-api-issues/issues/detail?id=1092 Pamela has indicated that the documentation of the sensor parameter will be made more prominent, including a comment in the "Hello world" example, and a key-generation code snippet that isn't invalid Javascript with a line break in it. The sensor=true_or_false will remain, though. Those changes should have happened a couple of weeks ago, I think, but it doesn't appear to have been achieved yet. Postings to the Group have been indicating for well over two years that the API key rejection message is at best badly worded and in most cases just plain wrong. What is vaguely helpful is the different "server has rejected your request" message, which indicates a problem with the sensor parameter. This sensor parameter thing is the largest single issue in the Group in the last three months, all caused by inadequate documentation. > - If you want to make user to take some choice about sensor param who > affects the code output please do it at input time, just where you asked me > for my username and URL. Now that is a good idea. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
