Re: [Google Maps API v3] Re: 2011/2/18 - New Release
On 12 April 2011 17:14, Mike Dolbow mike.dol...@state.mn.us wrote: Actually, I LIKE the fix as described by Chris: Labels are now on by default when Satellite mode clicked from map type control. To me, that's what the majority of users want when they click onSatellite: the aerial/satellite imagery beneath the labels, that provide critical context. Without that context, many users would be lost on the map. That's been the default behavior you get on the main maps.google.com page for years. I wanted to post here to say bravo to this change, because I set my mashups back to 3.3 until it took place. But of course, you still have the option to create what you call a clean map: just set your default 'mapTypeId: google.maps.MapTypeId.SATELLITE' in your mapoptions. That doesnt work it you want to open in map mode (or other custom map type), but allow switching to satalite (only). If you add SATELLITE to mapTypeIds (even *without* HYBRID) then you still get labels enabled when switching :( Its not just 'by default' - its on automatically, if you want it or not :) -- 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.
Re: [Google Maps API v3] Re: 2011/2/18 - New Release
Yup, you're right - my solution only works if you want to *start *in
SATELLITE mode. And the behavior you describe is what I *prefer *for
automatic behavior. And I suspect we could poll users and get 50% of them
agreeing with me, 50% agreeing with you. But I always go back to how it
generally appears in maps.google.com as how my users will *expect *it to
work. (Even though the switching mechanism is slightly different in
maps.google.com now, with the bigger buttons, when you switch to Satellite
view, you get labels on by default.)
The only way I know how to accomplish what you're looking for is to point to
version 3.3 and add the following to your map options:
mapTypeControlOptions: {
mapTypeIds: [google.maps.MapTypeId.ROADMAP,
google.maps.MapTypeId.SATELLITE]
},
With version 3.3, even if you start at ROADMAP type, the above
typecontroloptions will get you your clean Satellite look.
--
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.
Re: [Google Maps API v3] Re: 2011/2/18 - New Release
New IE6 javascript errors in API v3.1, v3.2, v3.3, v3.4 Hi, As of this morning (February 18th), I'm getting javascript errors in IE6 across all versions of API v3 (3.1, 3.2, 3.3 and 3.4). The error is: Line: 28 Error:Failed The map still loads, but there are no controls visible. Up until today, I've been able to use API v3 in IE6 without any major problems, so something must have changed in the API code. You can see the error when viewing http://code.google.com/apis/maps/documentation/javascript/examples/map-simple.html Sorry for harping on about IE6, but we have a large customer base and still have a significant number of IE6 users... Any help appreciated! Gavin -- 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.
Re: [Google Maps API v3] Re: 2011/2/18 - New Release
Wow that was quick - it seems to have been fixed now. Thanks! Gavin -- 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.
Re: [Google Maps API v3] Re: 2011/2/18 - New Release
And it's back again. I guess I'm being served different code from different server clusters whilst the change is propagated around. I'll post this in the bug tracker for API v3. Regards, Gavin -- 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.
Re: [Google Maps API v3] Re: 2011/2/18 - New Release
Hi Nick, Have you got a link to your page? It's possible a change in this release caused this problem for you. Cheers Chris On Fri, Feb 18, 2011 at 1:55 PM, Nick Small nick.ciagrat...@gmail.comwrote: Hey Chris, The new controls look great, no problems there. But I do have a bug that's popped up in 3.4, possibly related to WebGL issues. A distant ancestor of my map div has -webkit-backface-visibility:hidden. This worked fine in 3.3, but now I'm getting all kinds of visual weirdness when my 3D transforms start firing on that ancestor div. Most prominently, the map ignores backface visibility and shows it's rear no matter what, until the animation completes and the whole thing gets removed from the DOM. But in addition it's causing visual oddities in some of its siblings. Sometimes certain divs will flicker, or disappear partially or completely (ex: one div gets cut in half; the left half continues its journey into the Z axis, the other just disappears), and sometimes, after the parent is no longer visible and in its flipped state, the map's backface sticks around. No parent or siblings to contain it, just a map backface floating in space! These behaviors seem to be completely random and change every time. Any idea what could be causing that? Everything else looks great, but I had to switch back to 3.3 in the meantime! Thanks for a great API, Nick -- 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. -- http://twitter.com/broady -- 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.
