So, you just put the code to build that in between the code to build
your content and the code to build your footer. I have had far fewer
problems with depth since I started using getNextHighestDepth()
consistently. You just build the code in the depth order that you
want. If you start with this:
buildHeader();
buildContent();
buildFooter();
and you want to add something between the content and the footer,
then just add it in between:
buildHeader();
buildContent();
buildMoreContent();
buildFooter();
Guess where the new stuff ends up? No figuring out what depth to
assign, no re-assigning depths, no collisions. Nice and simple.
Nathan
http://www.nathanderksen.com
On Feb 3, 2006, at 11:35 AM, ryanm wrote:
No, but what Ryan describes is exactly what getNextHighestDepth()
is for.
Not at all. If you have a content container at 1, a navigation
container at 2 (so that drop downs lay on top of the content), and
a footer container at 3, and you need to add another content
container (for rotating ads or something), you want it to be next
to the other content in depth so that it's under the navigation.
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
