Components mess with depth?

[praufet]

So my movie was work all good and well then I added some text inputs and then it started messing up the depth on movie kept popping on top of another even though it shouldn't and didn't before I added the component. Then when I removed the component from the library, it all went back to normal, any ideas why?

[red penguin]

depth of what?

That first sentence kinda runs on there.

[praufet]

sorry. I have a ghetto preloader mc I made and it sits on top of everything. when I have any components in my library one of the mcs on the stage keeps popping up above it.

[red penguin]

"sits on top of everything"

So it is on it's own layer on the Stage. Top layer?

And magically "one of the mcs" is swapping depths somehow and blocks out the "ghetto preloader" ?

[praufet]

yes. The mc that jumps above is a tabstrip I made. Nothing else pops above it. The load is on the top most layer. Any ideas? It only happens where theres a ui component in the library.

[red penguin]

swap depths issue?

no clue.

[praufet]

any ideas anyone?

[emergency_pants]

I know why... it's because the components are really really really really cack in Flash. :mad:

Have you tried renaming the offending movieClip? It may have an instanceName that is conflicting with a variable in the components script... the actionscripts inside the components is really overblown, so maybe it's something like that?

Does it happen with any component? or just one particular type?

[praufet]

Any component. I'm trying to get a text input on there. I tried in with text input, numeric stepper, and combo box. I think I tried some others, but those I know for sure.

[red penguin]

can we see this happen somewhere?

[praufet]

I tried to create a sample movie but couldn't get it to work. Sorry, is there some kind of alternative to a the text input?

[theflux]

I think I may be having a similar problem with components screwing with depth.

I have a project which was already having a few difficulties with depth: After an SWF which contained a library full of components was loaded as an MC, my getNextHighestDepth function positively flips out on the main timeline. It starts giving me values for which removeMovieClip dont work.

I tried adding a button component to the main SWF (it previously had no components in its library and was working fine) to test something else but it also screwed my depths way up. Just having it in the library caused the very first call to getNextHighestDepth to return 1048576.

[Tilly]

I've also exact the same problem. When I use a component (on stage or in the library) the nextHighestDepth() returns an absurd high value of 1048576 and it really screws up my interface, because removeMovieClip() won't work properly. :mad: It drives me crazy and forces me to build my own UI components, which takes more time but at least act normally ;-)

Anyone who uses components on a regular basis know a solution to this?

Cheers,

Tilly

[Tilly]

I've discovered that using: unloadMovie() instead of removeMovieClip() works for me.

Cheers,

Tilly

[deadbeat]

It is the Macromedia core classes - mx.managers.DepthManager uses weird depths for the components...it is pretty easy to see it in action - create a new Flash Movie, and put this on the first frame:

trace(_root.getNextHighestDepth());

Then drag a component to the stage and Test Movie...

K.