Comments on: Deferred Component Instantiation in Actionscript

By: Ashine

Ashine — Mon, 19 Jul 2010 16:35:43 +0000

Thats a superb post.
Thanks for sharing these with us.
I have one more doubt on same lines, I have posted it on Stackoverflow, can you plz help me here ? Link
“http://stackoverflow.com/questions/3265411/difference-between-array-and-array-collection-in-flex/3265732#3265732″

By: Pie21

Pie21 — Sun, 23 May 2010 08:37:54 +0000

Great catch!

In my case, I have a main ViewStack (of VBoxes) controlled by a LinkBar. I have two states, before and after the user logs in. In the ‘before’ state they can only see the home page, but in the ‘after’ state, they can access all the pages.

The correct solution then is to only have the home page on the view stack initially, and then add the other pages once the user logs in. The problem was that adding the pages would cause them to load all their children, so when the state changed, all the non-home page pages would be completely created.

Without states, deferred instantiation worked as expected, and with this fix it now works as expected WITH states as well. Each page sets its creationPolicy=”none” (in the first (VBox) tag of the MXML definition), and it is loaded by the ViewStack container when the user switches to it.

Again, bravo!

By: riba

riba — Tue, 04 May 2010 20:13:29 +0000

You da man! That was exactly what I was looking for!

By: Jonathan Campos

Jonathan Campos — Mon, 28 Sep 2009 13:53:15 +0000

The process of deferring component instantiation within a container and for a viewstack is a bit different but with the same goal, improved performance.

Neil, for your question let’s use the example of having a really long page with multiple containers. It’s stupid to instantiate components that are off the screen, so we can wait till the scroll bar or view port gets to a specific value and then start to instantiate the container’s children components.

This would be a good use of the createComponentFromDescriptor or createComponentsFromDescriptors. Then when your case is hit you can call vbox.createComponentsFromDescriptors(true); Now all the children components that you originally set the creationPolicy to ContainerCreationPoicy.NONE to be created.

That help?

By: Neil

Neil — Mon, 28 Sep 2009 10:07:45 +0000

Great post, one thing I would like to know. If you are not using a TabNavigator but some other container, how would one go about instantiating the children using createComponentFromDescriptor as it seems that only MXML components are in this array, not the ones created dynamically.

Thanks

By: Devin Reimer

Devin Reimer — Wed, 22 Jul 2009 16:13:40 +0000

Thank you sooo much, I’ve been fighting with this issue for 3 hours, it never occurred to me that setting the creation policy to none on the individual components would be neccessary. After reading at least 50 blogs, finally I discovered yours.

Thanks

By: Hussein Grant

Hussein Grant — Sat, 20 Jun 2009 03:09:24 +0000

THANK YOU!! THANK YOU!!

You saved me hours!!! of debugging. I spent about 2 hours already trying to solve this problem.
Thank you again.