My main concern on this capturing is the conversion between the x-y position, the relative offsets and the transformation you'll have to do with the chart itself. You will have to dive into the SVG to search for the relevant (or closest) text object.
I fear for your sanity ;-) On Sun, Nov 20, 2011 at 8:51 PM, Matt Nuttall <[email protected]>wrote: > Hi TheNez; > > Thanks again for the reply! > > Yeah, I don't mind where the user clicks, as long as I get the region > returned from geochart, it is the use that has defined where on the region > they have chosen to click (i.e. if the user clicks close to the border of, > say, Alberta, that is just fine -- I'll still want to put an "x" on the > exact spot the user has clicked. It would be crazy for me to write a whole > new canvas just to be able to capture information that we know the Google > geochart visualization can provide to my code.... > > I'm still sifting through the Google visualization DOM hoping to stumble > upon some way of accessing clientX and clientY from the preceding onclick > event. > > If you come up with any more ideas, I'm all ears! > > Cheers -- Matt > > -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-visualization-api/-/0QpMLPdGpKYJ. > 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-visualization-api?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Visualization 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-visualization-api?hl=en.
