Remember that everything added to an API set makes the API larger, slower, harder to load, etc. If only 1% of users want to use a function, and it's a matter of 20 lines of javascript for those users to add it themselves, why would you want to burden the other 99%?
The development team does (I think) a very good job of adding that which is truly useful, and leaving out the "nice-to-haves." So don't feel bad if your pet function is not picked up. - Jeff On Feb 7, 3:12 am, Rossko <ros...@culzean.clara.co.uk> wrote: > > It took time to find that function to me (I dont remember the source). It > > could certainly be added to the API set. > > Why? Circle() exists already and has a getBounds() method > Is there a problem with that? (might not work well at the poles for > example, not much does in Mercator) -- 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 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.
