Thanks for adding it.

To get the error you can just create a button with the following code,
and then just click the button rapidly:

 if(map.viewMode == View.VIEWMODE_2D) {
                map.viewMode = View.VIEWMODE_PERSPECTIVE;
        } else {
                map.viewMode = View.VIEWMODE_2D;
        }

Assuming your machine isn't a complete monster, the following error
should come up:

ArgumentError: Error #2025: The supplied DisplayObject must be a child
of the caller.
        at flash.display::DisplayObjectContainer/removeChild()
        at com.google.maps.core::TilePane/unloadTile()
        at com.google.maps.core::TilePane/deleteAllTiles()
        at com.google.maps.core::TilePane/clear()
        at com.google.maps.core::ZoomLayer/clear()
        at com.google.maps.managers::TileManager/destroy()
        at com.google.maps.core::MapImpl/activateTileManager()
        at com.google.maps.core::MapImpl/set viewMode()
        at com.google.maps::Map3D/set viewMode()
        at test/changeMode()[test.mxml:76]
        at test/__modeButton_click()[test.mxml:26]

I fixed the problem by just putting a delay in between view mode
changes, I don't know how often people will run into this, it will
definitely show up if they have a button to swap between views.

As for the info graphic, I figured out the (or my) confusion,
essentially the way you guys have it is the map is on the floor and
the camera is looking down at it, so the info graphic is misleading.
Not really a show stopper.

On Sep 6, 3:18 am, "pamela fox (Google employee)"
<[email protected]> wrote:
> Hi Jonathan-
>
> Thanks for the reports.
>
> I've replicated the dragging bug and filed it in the issue tracker so
> that you can star it and be notified of 
> updates:http://code.google.com/p/gmaps-api-issues/issues/detail?id=1665
>
> As for the switching view bug, the only error that I've managed to
> replicate is if I try to set the viewMode before the onMapReady event.
> Can you give further steps/code for replicating, and indicate the
> actual error that you see?
>
> As for the Attitude, I believe the problem lies in our diagram being
> misleading. The best way to understand them is to play with the
> sample, and experiment yourself. We'll discuss making the diagram more
> clear.
>
> - pamela
>
> On Sep 6, 1:40 pm, Jonathan Wagner <[email protected]> wrote:
>
>
>
> > A couple of details, for the Attitude class, in the documentation it
> > says it is yaw,pitch,roll, but the yaw of attitude appears to actually
> > modify the roll, I could be incorrect if setAttitude doesn't modify
> > the camera, but the map itself, it's just a little misleading
> > according to the attached infographic.
>
> > Next, I posted this bug in a different thread, but I will include it
> > here as well. Dragging doesn't work as expected in View.VIEWMODE_2D,
> > if you zoom all the way out, map dragging only works in the middle,
> > not on the far edges.
>
> > Also when switching from one view to another perspective/2D an error
> > is thrown if the previous view is not finished initializing.
>
> > Other then that, it works great, thanks for your great work!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API For Flash" 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-for-flash?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to