The "Number expected" error occurs in the panTo() call in 
recursiveShift() in situations where it gets called before the geocoding 
reply has come back. Your myLong variable is calculated as
   "undefined" - 0.008
which gives the result NotANumber. Other browsers allow you to get away 
with that, but MSIE throws an error deep in the API code.


The "Invalid argument" error appears to have nothing to do with the 
Google API. It occurs deep inside the jQuery code, when it tries to set 
the style of an element to have height = "undefinedpx".

-- 
Mike Williams
http://econym.org.uk/gmap



--~--~---------~--~----~------------~-------~--~----~
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