As many of you may have already noticed, v2.193 was pushed out to v=2.s. While we're aware of the performance concerns regarding polys, we would've been unable to address this in the 2.193 release. Has anyone been able to compare poly performance between v2 and v3?
On Jun 11, 4:07 am, Maurizio <[email protected]> wrote: > Dear all, > in this time of change...I just realised my creature..the London > Profiler is not working anymore.. > and I suspect it is for the changes in the API.. > Something happened in the week end..as I could access it last > Saturday.. > Can anyone give me a hint? I suspect the reason is a 'wrong' API due > to modularization...www.londonprofiler.org > I would like to migrate to V3 but will I be able to use my custom > overlay function without problems...I suspect that with version 3 We > will also have to tweak our GMapCreator... > Many Many Many thanks!!! > Maurizio Gibin > > On 26 May, 02:37, jeko <[email protected]> wrote: > > > > > Hi Dann, > > > In testing 2.193 I've found that there are a lot of changes to street > > view over earlier versions. > > > Most work just fine for us, but the addition of a built in address > > overlay really crowds the UI when street view is shown at small sizes > > -- you can lose about half of the clickable area to the unwanted > > overlay and there's apparently no way to disable it. We use street > > view in a small widget on thousands of partner sites so this is pretty > > disruptive for us. > > > There's already a request filed for this (option to hide that address > > overlay), which I've just added a comment to, but wanted to post here > > as well.http://code.google.com/p/gmaps-api-issues/issues/detail?id=1920 > > > Please contact me off-list if you'd like to see a demo of how this > > affects our deployed widget and any other users of street view at > > small sizes (can give you access to our staging site) > > > Thanks, > > Jesse > > > On Apr 13, 11:31 am, Daniel Lee <[email protected]> wrote: > > > > *** Important information regarding version 2.s below *** > > > > The current stable release version (v=2.s) is set to version 2.140. > > > Over the past few months, we carefully reviewed all recent releases of > > > the Maps API and selected version 2.193 to become the next suitable > > > stable release version, otherwise specified as v=2.s. On June 15th, > > > 2010, all Maps API versions prior to version 2.193 will be deprecated > > > and no longer accessible. On and after June 15th, any site still > > > specifying an earlier particular version (e.g. v=2.140) will > > > automatically be pushed up to the new version 2.193. If this is > > > applicable to you, there are steps you can take to ensure your > > > application continues to function properly on and after the > > > deprecation date. > > > > If your Maps API application is using version 2.s or a version prior > > > to 2.193, begin preparing for this change *now*. Test your > > > application(s) against version 2.193. Alternatively, you can also > > > test them against v=2 which is currently set to version 2.208. If > > > you're not sure how to use a specific version, see this section on > > > "API Updates":http://code.google.com/apis/maps/documentation/#API_Updates > > > > As you're testing your application(s) against v=2.193 and/or v=2, file > > > bugs for any potential regression issues you encounter in the Issue > > > Tracker. It's really important for us to become aware of potential > > > issues in > > > advance.http://code.google.com/p/gmaps-api-issues/issues/entry?template=JS%20... > > > > ==== > > > > As always, let us know if you have any questions, comments, or > > > feedback! > > > > Dann -- You received this message because you are subscribed to the Google Groups "Google Maps 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-maps-api?hl=en.
