Actually, continuousZoom is not totally broken -- it works from the mouse wheel, but not on doubleclick any more. The zoom on doubleclick still works, but not continuously.
http://wxdev.gladstonefamily.net/test193.html will demonstrate the problem. Just doubleclick and you will see that there is no zoom effect. Now use the mousewheel to zoom and observe the zoom effect. It looks as though there is some sort of caching issue as you can get the continuous zoom to work on doubleclick after a time. Philip On Dec 17, 10:15 pm, Philip <[email protected]> wrote: > Indeed. Of course, thy just switched v=2 to 2.193c and now I see a > whole load of different errors! > > [Thu Dec 17 20:52:06 2009] psk-error: Error: 'null' is null or not an > object in function(a,b){var c=this.wu[b],d=K(c.x+a.lng()*this.yu > [b]);a=se(Math.sin(Qe(a.lat())),-0.9999,0.9999);b=K(c.y+0.5*Math.log > ((1+a)/(1-a))*-this.zu[b]);return new S(d,b)} > [Thu Dec 17 20:52:06 2009] psk-error: > inhttp://maps.gstatic.com/intl/en_ALL/mapfiles/193c/maps2.api/main.js > ($Date: 2009/11/28 14:11:51 $, GMap 2.193c) at line 600 > [Thu Dec 17 20:52:06 2009] psk-error: User-agent: Mozilla/4.0 > (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; GTB6; .NET CLR > 1.0.3705; Media Center PC 2.8; .NET CLR 1.1.4322; .NET CLR > 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) > > This update has also broken continuousZoom for me :-( The behavior > of setUIToDefault also changed a bit, but I could fix that one easily. > > Philip > > On Dec 17, 11:28 am, "[email protected]" <[email protected]> > wrote: > > > On Dec 17, 8:01 am, Rossko <[email protected]> wrote: > > > > > If you look athttp://pond1.gladstonefamily.net/errorrate.pngthenyou > > > > can see the sort of trending information that I collect. The big spike > > > > was when google switched to 2.140g. The end of the spike corresponds > > > > to when I changed my code to work better with whatever change they had > > > > made in the 2.140g version. It also appears that the transition from > > > > 180e to 184a roughly halved the number of errors that I am seeing. > > > > Not sure what you're expecting anyone to do about it. It is not > > > uncommon that one version of the API may silently ignore programming > > > errors which another version doesn't. Examples of that kind of thing > > > include : the use of string instead of number variable for > > > coordinates, non-integer values for zooms, etc etc. > > > > To fix anything like that you need to look at the client side code, no > > > amount of studying graphs of error logs against API versions will fix > > > it for you. You've already described that process yourself in > > > relation to 2.140g. > > > I don't think he is expecting anyone to do anything about it (except > > perhaps google). It looks like interesting data that could be > > valuable to the community. > > > -- Larry > > -- 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.
