> The reason you lose ordering might be that some of your rules are > spitting out HTML and others are populating aInvocations (which then > spits out HTML in the final step of the container execution). > > The way around it could be to populate the aInvocations array with the > HTML output from your rule -- rather than writing the HTML direct. > > Hope that helps,
I know that messing with the core is a bad thing. But I really think that instead of doing a "workaround" to make things work in a certain way I rather change the way that the container.cfc handles it all. These things are the little ones that makes it hard for new users to understand how it all works. I think that the rules shall be displayed in the order that I tell them to, regardless on what the rules contains. Not have to do it in a certain way to get where I want because of the core. For everything, if possible, the best solution for the new user is that things happen with a logic "If I do this, then this will happen (if not stated otherwise in the docs)". Thanks. Daniel --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
