On Jan 6, 1:33 pm, Philip <[email protected]> wrote: > This problem still happens in 2.140g, but the text of the function has > changed:
It's still the same function. Its subordinate calls will be renamed in each issue of the API. I think it would help if you could simplify your code. That might be a tall order, so it would also help if problematic data could be fixed -- that is, set in stone, saved as a flat file -- and then the published code amended so it used that flat file. It makes things really difficult to debug if the data changes and errors disappear. 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 -~----------~----~----~----~------~----~------~--~---
