This content has been marked as final. Show 3 replies
Check out the preloader docs in help system.
Thanks. Your answer wasn't the solution in and of itself, but it did get me thinking more clearly about the problem.
Instead of instantiating my map with the application's creationComplete event, which also dismisses the Preloader, I instantiated it with the application's initialize event, so now the map is on-screen before the Preloader is dismissed.
I'm still perplexed as to why everything is on-screen when the Application's creationComplete event is dispatched, but the map dispatches its creationComplete event before it's actually on-screen... but I guess I can just accept that it works now and stop asking why.
The map dispatches its creationComplete event because it is fully created, but that does not mean it has been added to the application. The creationComplete event for the application means the application has been created, which includes adding all the other components.
In a sense, the map does not need to be onscreen when it dispatches creationComplete, because the application itself is not yet fully valid. I guess that's why the preloader and initialize event exist, to do stuff before the app should be considered fully valid or "complete".