On 14 мар, 12:37, Mike Williams <[email protected]> wrote:
> You can improve on that slightly by listening for > "infowindowprepareopen" instead of "infowindowopen". > > "infowindowprepareopen" was previously a documented function at one > time, but it isn't now. I don't know what implications that has for > futureproofness. Thanks, but futureproofness is crucial for us. If an event is undocumented, we cannot use it. > >After we retrieve <name>, we place the GMarker on clicked point. Later > >user can direct us to load new KML file via GGeoXml, but after new > ><Placemark> is loaded, we cannot programmatically trigger > >"infowindowopen" event on a <Placemark> just UNDER GMarker. > > I've absolutely no idea what you mean. My English is really bad, I know. :) I am Russian, and never learned it. :) I mean, 1. after eating first "infowindowopen", 2. if user directed us to load another coverage map via GGeoXml, AND if there is another KML-derived object under previously clicked point 3. we have a need to programmatically trigger "infowindowopen" event to retrieve object's <name>. Because user cannot click exactly one point twice. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
