This content has been marked as final. Show 3 replies
bump. please, does anybody have any clues?
I don't know why it seems I can never get any help here? I try to post solutions for people whenever I can. Are my questions really stupid and/or really unusual? Can anyone suggest better help forum or community that is more active?
If anybody cares, setting the creationPolicy to ContainerCreationPolicy.NONE and then using createComponentsFromDescriptors() when needed has been a solution for my app. I was able to radically improve the perceived speed.
It causes some other weird side effects, but I'm working through those.
I'm not sure who moderates, but I can send you in the right direction.
Short answer: Look around for Asynchronous Flex demos
Running one task at a time is considered a synchronous (serial) request. What you need to do is make an asynchronous (parallel) request. In the web world, that's the 'A' in Ajax. By making asynchronous requests, you free up the main 'thread', while a separate worker thread is off completing the task. This keeps your interface responsive.
I think that leads to event listeners.. Send off a background request, but listen for it to complete. Link the listener to a second piece of code upon successful completion.
I wish I could get into more detail, but I'm not a Flex guy.. hoped that at least helped gel the idea.