On Mar 6, 1:46 am, sgiddings <[email protected]> wrote: > I had developed my code relying on the undocumented, but referenced, object > pixelBounds for aligning my custom info overlay. > After having requested that this be documented and fixed, it was removed in > the version 3.4 release (despite the change request having been accepted). > > So, in order to be able to continue with development, I have referenced the > version 3.2 as per the instructions for choosing an API version. > To my surprise, this version has also been changed, removing the pixelBounds > object as well. > > Can we really rely on the versioning process to access "frozen" code ? > Does frozen really mean "not to be touched again" ?
Yes. But (from the documentatio): http://code.google.com/apis/maps/documentation/javascript/basics.html#Versioning + When we release a new numbered version, we will "freeze" the + previous release version, meaning that we will no longer update it + with any code changes, including bug fixes, ensuring it is + completely stable. Each time we introduce a new frozen version in + this manner we will retire the existing frozen version. That is, at + any given time there will be only one frozen version available. + Applications requesting numbered versions that have been retired + will automatically receive the current frozen version. When they release a new version the last "frozen version" goes away. -- Larry -- 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 [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-maps-js-api-v3?hl=en.
