This content has been marked as final. Show 6 replies
some components occupy the highest removable depth which causes problems the problems you see when they are used with nextNextHighestDepth(). there's a depth manager component that should remedy the problem, but i find it easier to manage depths explicitly with a variable.
getNextHighestDepth() tends to interfere with the v2 components because those components use reserved depths. if you want to configure depths for assets when using v2 components, use the Depthmanager class.
Yep... I swapDepth before removing the pop-up window to deal with that issue.
Attached is the code I suspect is ultimately responsible. Basically, the helpwin function is called displaying the pop-up. THen, when the button on the pop-up is called, the hidewin function is called to hide it. After this point, strange things happen.... as mentioned in my previous post.
THis is only an issue after a component has been added. Otherwise everything is fine.
I don't think most of the code here is relevant, but I'm going to post the entire functions just in case.
did you read either of the two posts that tell you how to remedy the problem?
I should have mentioned that I tried what you suggested... It makes no difference....
My understanding was that using getNextHighestDepth would interfere with the removing of a movieClip (not the mouse events after a clip has already been removed)
I just tried it again to make sure. I set a variable to a specific number, then used that variable in place of each getNextHighestDepth. Finally, I removed the swapDepths. Is there anything else I am missing?
that's a v2 component bug. you might be able to resolve that problem if you use the focusmanager class. otherwise, don't use the offending components.