I have done the same as Mike and the only way to make it work in only one or two second is open a new window as he did in test 3.
Please I need also to show a google map in my air app without opening a new window. I am using 1.18 and 1.19 doesn`t works at all. Thanks, Juan On Sep 29, 3:46 pm, wymetyme <[email protected]> wrote: > I can confirm this same experiment in my own app. What is the point in > releasing compatibility with AIR if it becomes unusable in a real- > world sized AIR application? It takes 15+ seconds for the map in > initialize in my app unless I use a new window. I tried to use a new > window to initialize the app and then load the app in my main app > later. This works for cutting down the initialization time and it even > loads the map in my main app EXCEPT functionality becomes broken in > the map (no dragging, etc). Can someone from Google please provide a > fix for this? There is no reason the initialization process should > have to send over the whole app in a bytearray (assuming thats the > bottleneck). It's been 2 months since this post has been opened and > still no fix. > > I am using SWC 1.19a. > > On Aug 19, 6:44 am, Mike Higuera <[email protected]> wrote: > > > I encountered this problem as well and did a little experiment with > > insightful results. > > > Test #1: I add the map to the current window in my full-sized > > application (includes several APIs and a few hundred classes). > > Result: Very slow initialization (about 30 seconds) > > > Test #2: I add the map to the current window in a very small test > > application (includes only the Google maps API and a couple of > > classes) > > Result: Much faster (about 5-10 seconds) > > > Test #3: From my full sized application, I instantiate a new Window, > > add a new map to it, and call myWindow.open() > > Result: Map loads instantaneously > > > In all three tests, I used the same construct for the map itself. The > > only difference was the size of the application it was running in. > > > I ran the Flex profiler and found that the delay in Tests #1 and #2 > > was in the Map.added() method. Digging further, it appeared that > > something was taking a very long time to convert to a ByteArray deep > > in some as3corelib classes. > > > My theory is that the API is trying to convert the Map's parent > > application into a ByteArray as part of the process to authorize me to > > use the API. That is why it is so much faster when I launch it inside > > of a new Window. The new Window belongs to the SystemManager rather > > than my application. Therefore, in Test #3, there is far less to > > convert into a ByteArray. Perhaps this also explains why it > > initializes faster when running as a stand-alone application--it is > > already in binary format. > > > Has anyone else profiled with similar results? Does this make sense? -- 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.
