You make it sound like I'm forcing it to work. I'm not forcing it, it
works as a nice byproduct of how I normally setup and group my movie
clips. I see this as being good coding practice. Things that are
grouped together share a parent movie clip, making control of the
group easier and making depth management easer as each movie clip
manages the depths of its children. I hate renumbering depths, and I
don't like having to figure out blocks of depths then later finding
that I need to move a block later on. This works very cleanly for me,
both from architecting movie clips into a logical hierarchy and from
preventing annoying depth collisions. I don't deny that it will not
work in all situations, nor did I claim so, nor do I know your
particular experiences with depth management. I do however have a
hard time imagining that manual depth management is a best practice.
Anyway, this has gone on long enough. If you haven't gotten the
point yet you're never going to.
Nonsense, this is a great debate IMHO, and I would love to hear more
from others as well. This is something that everyone has to deal
with, and I genuinely thought that others would make more use of
getNextHighestDepth() and was surprised that you and others avoid it.
What are the situations that you have come across where only manual
depth management would work? Do you have other ways of managing depth?
Nathan
http://www.nathanderksen.com
On Feb 6, 2006, at 3:10 PM, ryanm wrote:
Then I create a placeholder movie clip...
You miss the point. Doing something because you can usually find
a way to make it work doesn't make it a valid replacement for good
coding practices. That you rarely come across a scenario that you
can't handle that way only means that there *are* scenarios that
won't work that way, and that it is likely that at least some of
the time when it does work for you it would still be better (more
efficient, more readable, etc) to do it a different way. Also, just
because you rarely run into situations that don't work that way
doesn't mean that others don't run into them all the time, which
means your method probably isn't the best one to be recommending
broadly in a thread about best practices. Why not pick a good,
standardized way to manage depths that works in every scenario?
Anyway, this has gone on long enough. If you haven't gotten the
point yet you're never going to.
ryanm
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
