Is there any way to delay flex from drawing anything until everything is ready to be rendered?

Question

I have this CustomVideoPlayer which uses a skinned VideoPlayer and a button for closing. The problem I see is that when going out of fullscreen mode I can litterally see how the subcomponents of the videoPlayer - background frame etc shrinks and repositions in the middle of the screen cause I have vertical and horizontalCenter and etc. So whiching between both states is not fluent. I don't want to animate it, I just want not to see the glitching resizing and repostioning.
So how can I "wait" till all elements are resized and repositioned in the normal state and then show the new state all at once with no glitching? Is it possible ?
And one more extra question:
I've taken a look inside the VideoPlayer class and I've noticed that when adding skin part for example PlayButton, they add a listener for Click, when they remove the part they remove it. That's ok but as component is removed from it's parent partRemoved is not called so the listener is never removed and would this make the component stuck in memory cause of that listener?
Oh and one more small extra question:
If a skin part is required does this also mean that it must exist in all states?
(cause if it does that would mean I could add it's event listeners in the creation complete or partAdded, but not partRemoved function, since it would never be removed...)

Answer 1

If I do this then I will have my video player in fullscreen disappear for a moment and then reappear out of fullscreen, and I want it not to disappear, but to just jump to the other state fully resized and repositioned with no glitching in between states.
Than you will need to implement your own solution which meets your specific design goals. That's the nature of the beast my friend.
As far as I know dynimic skin parts have another meaning - creating more than one instance at runtime. Also I've read just now (again) partAdded and partRemoved are called on component initialization and skin change. So basicly if I change the skin, it makes sense to remove the eventListeners from the old skin parts. But still, I've read on many places that if an object has event listeners attached to it it will Not be GC unless they are weak, so it will be stuck in memory forever.
So looking at the VideoPlayer and it's skin parts, I'm not seeing any event listener being removed when I remove the instance I have of the VideoPlayer. Why is that? Why the component does not remove it's skin parts event listeners?
Are you changing skins? If so, I bet the parts would be removed as expected. The partRemoved method is not being called because it's not needed. If you remove the parent component, than any reference encapuslated within that component are removed as well.Fire up the profiler if you don't believe me.
I'm interested in the skin parts and states relation. With includeIn and excludeFrom you define in which states the component is added to or removed from as a child (element). So If I have a skin part which is required=true and I have 2 states from one of which it is excluded... whouldn't that result in a runtime error since the part is not there but it is required?
I'm pretty sure that it only checks if the instance exists, and does not care if it has been created and added to the display list. I do not really know for certain though. This could easily be answered with a simple test.