With all of that said, my initial thought was that bShowIfEmpty should be false, but I could see it defaulting to true to maintain a consistency with the current container tag's behavior.
This was my thinking, existing sites work the way they are, those that want to display things differently use the new attribute. Makes the update process smoother for existing sites.
If you think there is potential for backward compatability issues then I guess default=true has to be the go :(
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
