On Oct 22, 12:54 am, Mike in Stroud <[EMAIL PROTECTED]> wrote:
> To be honest you should only use v=2.x for testing purposes as it will
> be very new and has not been tested outside of Google, and things can
> change before it becomes v=2
> Kind of like a beta version I guess!
>
> Most people will
To be honest you should only use v=2.x for testing purposes as it will
be very new and has not been tested outside of Google, and things can
change before it becomes v=2
Kind of like a beta version I guess!
Most people will use v=2 as this is one version down from v2.x so will
have any problems i
On Oct 21, 8:11 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I'm aware a new version of the 2.x
> api was released (and saw the post related to it that went out ~4am
> Oct 20), but is there anything to describe what we were seeing with
> version 2.s?
Not without a link which demonstrates
We have a map application that was previously set to version 2.x,
which suddenly failed (just yesterday, Oct 20 it seems) to properly
render the info windows and overlays. After much debugging and
research, we changed it last evening to 2.s and saw it functioning
properly. However, this morning we
