String, you're absolutely right. Reading when the events fire, I should have called it on "addoverlay" instead of on "load." I've switched to "addoverlay" and the initial call to _IG_AdjustIFrameHeight fires correctly now.
Unfortunately, _IG_AdjustIFrameHeight still fails to fire on other calls in the code, such SUBSEQUENT submissions to the form, or is left blank. This could certainly be another instance of the API correcting an old bug that I had been accidentally exploiting, as above. But most of the calls to _IG_AdjustIFrameHeight, such as when the form is left blank and the map/directions are rehidden, are incredibly straightforward and I'm not seeing why _IG_AdjustIFrameHeight would fail to fire. On Jun 24, 5:06 am, String <[email protected]> wrote: > On Jun 23, 7:02 pm, skeeJay <[email protected]> wrote: > > > That's correct. You should be able to see textual directions below > > the map. It still works correctly in syndication, such as > > athttp://kalafarski.com/directions/ > > Looking at this in more detail, I suspect that this isn't actually an > iGoogle problem as such. > > You're calling _IG_AdjustIFrameHeight in the GDirections load event > handler, but the docs for that event specifically say that 'The "load" > event is triggered before any overlay elements are added to the map/ > panel.' And sure enough, when I drop a breakpoint on your > _IG_AdjustIFrameHeight call, the text directions below the map aren't > there yet. > > It's been a while since I used GDirections, but I think the event you > want is actually addoverlay: 'This event is triggered after the > polyline and/or textual directions components are added to the map and/ > or DIV elements.' > [fromhttp://code.google.com/apis/maps/documentation/reference.html#GDirect...] > > Why did this used to work and just stop now, I hear you ask? Either > something changed in the GMaps API, or more likely, the new > gadgets.window.adjustHeight function simply exposes a hole that was > always there. IIRC, the Legacy _IG_AdjustIFrameHeight had a timeout > built into it; it's quite possible that it just happened to wait long > enough for the GDirections to finish its work. In fact, I'd guess that > it did fail occasionally, but not consistently enough to be a problem. > > HTH, > > String --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" 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-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
