On Sep 28, 7:17 pm, octogoi <[EMAIL PROTECTED]> wrote: > > But It doesn't in this case. As I said, when gmaps goes from maximized > to restored infowindow, it does some panning. But it does not fully > return the view to the position prior to the maximization.
As Esa said, you're trying to get the API to do something it's not designed to do. > As I said, my goal is to move smoothly from a maximized infowindow to > a restored infowindow at the exact view the map had prior to > maximization. The users of the map will maximize/restore windows a lot > and so I do not want that to be noticeably jittery. I don't think it's possible to get the restore animation to move to the saved position, you will need to do it in your code. You *still* haven't provided a link, so we've no idea how "jittery" your "jittery" actually is, or how you are doing it. Have a look at http://andrew.leach.1.googlepages.com/maxcontent_simple.htm -- currently this uses a "restoreclick" event to pan the map back to where it came from. It's a bit jittery, I suppose, depending on processor/video speed. If you change it to a "restoreend" event, it's beautifully smooth, but two-stage. I can't think of another way of doing it, but I'm open to suggestions. Frankly I reckon it's better to allow the API to work the way it's designed to work. You could see if there is a relevant Issue in the issue log, and add an enhancement request if there isn't one. http://code.google.com/p/gmaps-api-issues/issues/list 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 -~----------~----~----~----~------~----~------~--~---
