Hi TheNez; Thanks for the update.
I already have actions that trigger off the returned region name. I know that the Google Visualization API is using the clientX and clientY values -- that's the way the API is able to return the region to my application. There is no reason the Visualization API could not expose the clientX and clientY values it is using. I've browsed the DOM for the Visualization and seen clientX and clientY referenced in several places. Exposing the coordinates would allow the Visualization API to not only provide the region name, but also the exact position within the region that the user is clicking on. For example, when my application is returned a region of US, was the user clicking on Alaska, Hawaii or continental United States? When you get down to the province/state level, the coordinates of the click are even more useful. Let's say I'm displaying the US map only: when the API returns, say, a region of US-CA (California), did the user click near San Diego or near San Francisco? I'd like to be able to provide a pull-down list to the user at the exact location they clicked. Then, after they make their selection I want to place a tiny amount of text at the exact location. Any of the Google Visualization API programmers have a comment? I'd sure be a happy programmer if this data can be exposed somehow. Thanks again -- 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/-/W5cQRV_3iwsJ. 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.
