If you want to get really dirty, I've cooked up something completely awful. I was interested in looking into how the map controls are created/added so I could find a better workaround for my control issues. I created this terrible piece of code: http://github.com/nickspacek/Google-Maps-V3-Hacks/blob/master/google.hooks.js
Right now all it lets me do is inspect the code in the controls.js file, and add a hook to track when the controls have been added to the map. Since all of the map components are loaded dynamically and run through an eval function (google.__gjsload_apilite__), we can hijack that and mess around with the eval string. DISCLAIMER; not for the faint of heart, you're screwing with the obfuscated Google code here! If you break anything it's not my fault. Don't say I didn't warn you! I don't recommend that anybody use this code.
-- 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...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
