On 4/26/07, Tom Chiverton <[EMAIL PROTECTED]> wrote: > > Well, point 1 is that if you're going to write: > <mx:Canvas xmlns:mx .... > <mx:VBox ... > why not just write: > <mx:VBox xmlns:mx ... > to start with.
that's perfectly reasonable, assuming you always use a vbox inside your canvas. I just looked at four of my views, and only one of them uses a VBox. The other three only have a datagrid and a couple of buttons, and I didn't need the Vbox in those cases. I just checked the other four views in my app, and none of them use a VBox. Two of them use Form components. I see your point though... don't just use a canvas.. use the right container for the job. But a VBox is not always the right container. I just happen to use all canvases because until this conversation, it never occurred to me to use anything else, since the examples for TabNavigator components always used Canvas components for the tabs. Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/Flex/message.cfm/messageid:3981 Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
