aha - I misunderstood 'working example' as this is the kind of thing
I want to do, my fault.
--
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-v3@googlegroups.com.
To
Larry - Can you explain how the domready listener is different than having
the click listener ready to roll once infoWindow.setContent(content) is
called.
On Tuesday, October 9, 2012 10:42:29 PM UTC-4, geoco...@gmail.com wrote:
On Oct 9, 12:23 pm, Quaye Trimble qtrim...@gmail.com wrote:
Well I thought I was on the right track. Creating the content and
parking it for later use seemed like a good method until I realized
grabbing the HTML to use inside the inforwindow breaks the chart display
because of the duplicate div id's.
On Wednesday, October 10, 2012 4:42:47 AM UTC-4,
On Oct 10, 6:06 am, Quaye Trimble qtrim...@gmail.com wrote:
Larry - Can you explain how the domready listener is different
than having the click listener ready to roll once
infoWindow.setContent(content) is called.
What do you mean by having the click listener ready to roll once
Well, I thought having the table row click handler ($('tr').live(click,
function()) inside the $(document).ready function, that it would be
listening for the click after the infowindow content is set
(infoWindow.setContent(content)). Your solution moved the table row click
handler into the
So if the domready listener is different than
$(document).ready, how is it different?
domready is an event fired by the Maps API, when it has finished
building an infowindow
https://developers.google.com/maps/documentation/javascript/reference#InfoWindow
$(document).ready is some jquery
On Oct 10, 11:13 am, Quaye Trimble qtrim...@gmail.com wrote:
Well, I thought having the table row click handler
($('tr').live(click,
Also, you should be aware that .live is deprecated:
http://api.jquery.com/live/
function()) inside the $(document).ready function, that it would
be listening
