> I hope, that my point of view is clear even my english:) Absolutely, it's a perfectly reasonable argument. "Make things idiot proof" is a good goal, but we all know in real life the idiots are very inventive :) That's not a dig at you, it's a common term for what you're asking.
> So > when gMap.setCenter MUST be called right after GMAP initialization > before any use of GMAP object, why it is not a part of GMAP > constructor? I don't know. Doing it seperately alows other non-GMap actions to be taken in between, such as finding out where to put the centre. > And i really don't want to debug > API to inspect API problem... But it wasn't an API problem in your case ... > Just take a look on this forum and its structure, constantly repeating > same questions and problems, wouldn't be better to analyze them and > make appropriate changes in the api to prevent them? An alternative tongue-in-cheek view ; looking at the sensor=true_or_false issue, it crops up again and again simply because they're not reading page one of the documentation, just blindly copy- pasting. Some of them at least will learn a lesson from it. 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 -~----------~----~----~----~------~----~------~--~---
