I'm using v3 and I read that map jumping was fixed in a release. I still get some map jumping for some reason. can't figure it out.
there's also an issue with latitude and longitude. I have no idea how it works with respect to custom tiles. what's the math to find out where a certain absolute point (x, y), relevant to the original image before splitting into tiles, is in latitude and longitude coordinates? I've remedied the situation by offsetting the coordinates given to getTileUrl but I'd really like to figure out what's going on with latitude and longitude. you can find my current implementation here: http://s11.info:2222/map/index.html note: yes I Know myLatlng is set to (0, 0) currently. I couldn't figure out what to set it to so I could centre it which is why I offset the tile coordinates in getTileUrl another note: for some reason there's no more map jumping after I offset the tile coordinates. odd. any help is much appreciated. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
