http://pskreporter.info/wxnearbylatest.html shows that the problem is
still there in 2.140g. From doing some more searching, it sounds very
like issue 833: http://code.google.com/p/gmaps-api-issues/issues/detail?id=833

However, 833 is marked as resolved in 2.140g, and this bug is still
present. However, in my case, I am invoking panTo rather than
setCenter during a continuousZoom.

Philip

On Jan 30, 12:20 am, Philip <[email protected]> wrote:
> warden [Andrew Leach - Maps API Guru] wrote:
>
>
>
> > On Jan 20, 1:40 pm, Philip <[email protected]> wrote:
> > > 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 don't have Firefox 3, but both pages show the zoom control and map-
> > type control in Firefox 2. You may have found a problem between the
> > Maps API v2.139 and a plug-in, perhaps. Firebug works in Firefox 3, so
> > presumably that will give a hint about what's going wrong in your
> > case.
>
> The problem exhibits itself in IE.
>
> If you look at
>
> http://pskreporter.info/wxnearby139.html
>
> this is much simpler test case. I would hazard a guess that it is to
> do with the fact I do the following (in this order):
>
> Create the GMap2 object
> setCenter   -- tight zoom to boston
> EnableContinuousZoom
> SetZoom  -- wide zoom
> PanTo  -- center of the US
>
> It doesn't fail every time in firefox 3.0, but pressing shift-reload a
> few times will show the problem (the map does not end up with the map
> type controls on it)
>
> In IE 6, you *sometimes* get "undefined" is null or not an object.
>
> If I remove the continuouszoom, then it doesn't seem to fail. If I
> remove the setzoom, then it doesn't seem to fail.
>
> This example is entirely standalone and (after editing in the
> appropriate key) will run anywhere.
>
> Maybe the above sequence of API calls is not allowed -- but they seem
> reasonable to me, and they worked just fine until version 2.139....
>
> Philip
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to