On 4/25/07, Ian Skinner <[EMAIL PROTECTED]> wrote: > > Ok, that worked! Now why did I have to do that?
good question. I'm not sure. I suspect it's because MXML components are actually classes, and thus vars that should normally be private (in your case, it should probably be private) would NOT be accessible inside the MXML components. Maybe the [Bindable] prefix just makes the variables accessable to the mxml components without having to use full path references like parentDocument.foobar and stuff. The simple answer: You had to do that because you tried binding a variable to a component, and variables created are not bindable by default. rick -- CFMBB - Coldfusion Message Boards, Version 1.21 Now Available! http://www.cfmbb.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/Flex/message.cfm/messageid:3960 Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
