New Release - 2011/3/17

[Chris Broadfoot (Google Employee)]

Hi all,

Today we pushed a new version of the API. This version brings some pretty nice features, as detailed in Thor's blog post here:

http://googlegeodevelopers.blogspot.com/2011/03/new-angle-on-world-with-45-imagery.html

We also pushed a new version to the stable release (3.3) that fixed a regression with Polygons.

In this release...

Resolved issues:

  * 45 Degree imagery (Issue 2412)

  * Overview map control (Issue 1470)

  * Support animated gifs - 'optimized' option added (Issue 3095)

  * Marker.getVisible() returns undefined (Issue 3114)

Noticeable changes:

  * Fixed: Circles and rectangles ignore zIndex

  * Fixed: Mouse events trigger events twice when Marker is animating

  * Fixed: Styled maps do not use styles if map type added to registry after map type id set

  * Fixed: Non-styled map types adopt the style of a Styled Map Type

  * Markers now fire MouseEvents, not DOM events

Cheers

Chris

--
http://twitter.com/broady

[Gary Little]

It would be nice to have a way to prevent the overview map control
from appearing when the map is printed. This could be done by
supporting an overviewMapControlOptions parameter for specifying the
name of a CSS class to be applied to the control's DIV. If this were
done, a display: none; rule in a @media print declaration could be
used to prevent printing. (This is the technique I use in the
KeyDragZoom library so that the programmer can control whether the
drag zoom control is printed.)

Gary


On Mar 17, 12:07 am, "Chris Broadfoot (Google Employee)"

<c...@google.com> wrote:
> Hi all,
>
> Today we pushed a new version of the API. This version brings some pretty

> nice features, as detailed in Thor's blog post here:http://googlegeodevelopers.blogspot.com/2011/03/new-angle-on-world-wi...

[Luke Mahé]

The Overview Map control shouldn't print at all. I've filed a internal issue about this. Feel free to file a external one too.

-- Luke

--
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-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Gary Little]

Probably all you (Google) have to do is set the class of the Overview
Map DIV to "gmnoprint". Undocumented for us, but OK for you to use!

Gary

[Nianwei Liu]

45 degree image is great!

However it still suffers problems of tilted/clasping walls due to
edgematching of images. Any view-port adjusted image tile solution
down the road? Will the classes exposed in API like in V2?

Also, it probably helpful to document the impact to certain overlays,
for example, GroundOverlay, and TileLayerOverlays like traffic,
panoramio, some KML layer and fusion table layer etc won't work under
45 map type due to incompatibility of projection, etc.

--Nianwei

[bratliff]

On Mar 17, 7:07 am, "Chris Broadfoot (Google Employee)"

<c...@google.com> wrote:
> Hi all,
>
> Today we pushed a new version of the API. This version brings some pretty

> nice features, as detailed in Thor's blog post here:http://googlegeodevelopers.blogspot.com/2011/03/new-angle-on-world-wi...

>
> We also pushed a new version to the stable release (3.3) that fixed a
> regression with Polygons.
>
> In this release...
>
> Resolved issues:
> * 45 Degree imagery (Issue 2412)
> * Overview map control (Issue 1470)
> * Support animated gifs - 'optimized' option added (Issue 3095)
> * Marker.getVisible() returns undefined (Issue 3114)
>
> Noticeable changes:
> * Fixed: Circles and rectangles ignore zIndex
> * Fixed: Mouse events trigger events twice when Marker is animating
> * Fixed: Styled maps do not use styles if map type added to registry after
> map type id set
> * Fixed: Non-styled map types adopt the style of a Styled Map Type
> * Markers now fire MouseEvents, not DOM events
>
> Cheers
> Chris

The support files:

http://maps.gstatic.com/cat_js/intl/en_us/mapfiles/api-3/4/5/{common,map,overlay}.js
http://maps.gstatic.com/cat_js/intl/en_us/mapfiles/api-3/4/5/{util,onion}.js
http://maps.gstatic.com/cat_js/intl/en_us/mapfiles/api-3/4/5/{controls,stats}.js
http://maps.gstatic.com/cat_js/intl/en_us/mapfiles/api-3/4/5/{marker}.js

are combined non-deterministically. Arbitrary file groups are cache
unfriendly. It might be beneficial to a first time user of his or her
first mapping application with an empty cache and a long latency
connection. Everyone else with a well stocked cache suffers.

Large files cannot be cached on some mobile devices like the iPhone.
Small equivalent files could be cached.

I do not use API markers in any of my applications. The file
"api-3/4/5/{marker}.js" is always loaded but never used.

[bratliff]

I am using Firefox.

I am unable to force the API to build CANVAS markers:

var test=new google.maps.Marker
({
map:cover,
position:new google.maps.LatLng(+40,-95),
clickable:false,
optimized:true,
zIndex:0
})

It builds markers using:

http://maps.gstatic.com/intl/en_us/mapfiles/markers/marker_sprite.png;

[jeren yao]

hello , have api V3 provided the functions of inquiring route for bus
or metro ? anybody can tell me ?

On 3月17日, 下午3时07分, "Chris Broadfoot (Google Employee)"

<c...@google.com> wrote:
> Hi all,
>
> Today we pushed a new version of the API. This version brings some pretty

> nice features, as detailed in Thor's blog post here:http://googlegeodevelopers.blogspot.com/2011/03/new-angle-on-world-wi...

[Gary Little]

Chris,

Note this Safari disappearing marker bug with V3.4 when marker
optimization is off:

http://code.google.com/p/gmaps-api-issues/issues/detail?id=3162

Gary

On Mar 17, 12:07 am, "Chris Broadfoot (Google Employee)"

<c...@google.com> wrote:
> Hi all,
>
> Today we pushed a new version of the API. This version brings some pretty

> nice features, as detailed in Thor's blog post here:http://googlegeodevelopers.blogspot.com/2011/03/new-angle-on-world-wi...

[Chris Broadfoot]

Unfortunately it is not feasible to put draggable markers below canvas markers.

So, unless you want all your draggable markers above canvas markers, it's necessary to specify optimized: false when creating your non-draggable markers.

Hope this helps,

Chris

[Jerry]

Hi,

> Today we pushed a new version of the API.

> Noticeable changes:

>   * Markers now fire MouseEvents, not DOM events

How do we get DOM events if we want them?

Are we supposed to be able to just call addDomListener instead of
addListener ? (I tried that, and it didn't seem to work.)

Link to map at: http://www.docspot.com/find?name=&location=94040&lat=37.3785351&lng=-122.08658500000001&filter=R718

(It used to be that if you mouse over a marker, you'd get something
like an info bubble, but one generated with a different library. Now,
that doesn't work because I only get a MouseEvent.)

Thanks,
Jerry

[Chris Broadfoot]

There's no DOM for a particular Marker anymore, so no DOM event is provided.

You can use the mouseover and mouseout events on Marker. This change does not limit this particular use case.

--
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-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

--
http://twitter.com/broady

[Jerry Lin]

Thanks for the response -- would you mind clarifying this comment?

> You can use the mouseover and mouseout events on Marker. This change does
> not limit this particular use case.

How would we get the mouseover DOM events for the Marker? (I assume
it's not addListener, since that only returns a MouseEvent. From my
testing addDomListener seems to return the same.)

Thanks,
Jerry

[Chris Broadfoot]

The API no longer uses DOM for detecting these events, so there's no DOM event to forward on.

What do you need DOM events for?

[Jerry Lin]

Hi Chris,

I found an external library to replace the functionality of Google
Maps' InfoBubble (I don't like how Google Maps' InfoBubble is so big,
and there's also some weirdness with mousing). The external library
needs a DOM event to know where to show up.

Regardless of the reason that I need the DOM event -- isn't this an
API change (the API used to provide DOM events and now provides
MouseEvents)? I get that the new API might be more lean and efficient
-- but isn't there some clause about support legacy APIs for some
number of years?

I tried specifying v=3.2 and still don't get DOM events. Is that expected?

Thanks for your help,
Jerry

[Chris Broadfoot]

Then the library you're using should be updated. You might be interested in Luke's InfoBubble library:

http://google-maps-utility-library-v3.googlecode.com/svn/trunk/infobubble/examples/example.html

The Event that was passed through on 'click' was never documented - sorry about that! Passing through a DOM event was not a documented "feature".

v=3.2 *should* get DOM events.

--
http://twitter.com/broady