It seems it has been reported months back that their is a significant
startup delay when using Google Maps for Flash in an AIR application.
There have been reports of an incomplete solution. The solution
apparently causes certain behaviors to no longer work (clicking,
dragging, etc.) when the map displays (not the temporary one used to
avoid the delay - hack).

I speak for myself but I'm sure now with the release of AIR for
Android this will only grow to be an even more critical issue for the
API as maps are such an important part of mobile apps. In my case its
the first thing that appears. Having a 10-15 second delay is just
awful.

Is there anyway someone can look into this and at least notify us of
what is wrong?

Or at least have the API team provide a fix for mobile developers
using Google Maps on AIR for Android?

Has anyone else out there experienced this or come up with a solution
on the mobile? I don't believe the new window solution will work on
AIR for Android.

-- 
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