I have a much simpler case that exhibits a similar problem between 2.138 and 2.139.
http://pskreporter.info/cgi-bin/wxnearby138.pl http://pskreporter.info/cgi-bin/wxnearby139.pl You will observe that (in particular) the zoom controls and the map type controls do not load in the 139 version. This is due to an error (in Firefox 3 at least). This is 100% reproducible, and does not depend on any external interaction. I suspect that since I am having a similar problem with two completely different pages of mine, then there is probably something about the way that I use the GMap2 object that 2.139 (and later) doesn't like. However, it would be nice to know what it doesn't like, and whether this is a bug on my side or on the GMap2 side or both! Thanks Philip On Jan 6, 9:42 am, "warden [Andrew Leach - Maps API Guru]" <[email protected]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
