> Note that even if your device does not use a sensing device, you must > still pass this parameter, setting its value to false."
How daft is that? It means that every existing instance of the Google Maps API is now acting against this requirement. Why not just treat sensor=false as the default? Google don't seem to be requiring this argument in GET requests yet, but if they do it'll break almost all the Google Maps API maps in the world... :( Yet another example of real-world technology moving too fast for the lawyers to keep up :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
