So with that said, is it safe to say that using the bindProperty method in AS, DOES release the memory it uses whenever the control gets destroyed? If this is in fact the case, that would be another huge deciding factor for me - since my Flex App is a HUGE Master/Detail type application, in which PopUp Windows are used extensively to display the extended information to the user. It's in these PopUp Windows, where I have to create all these bindings, so that the ValueObjects which reside in the Model, get properly updated when the user changes the information. This is an interesting subject, and I hope it gets discussed further :) Thanks everybody so far, for all your help and insights. Mike
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Xavi Beumala Sent: Saturday, January 20, 2007 1:29 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] BindingUtils.bindProperty versus <mx:Binding> On 1/20/07, Alex Uhlmann <[EMAIL PROTECTED]> wrote: I'd question why you would want to replace all our MXML bindings when it's working like a charm for you? ;) Aren't MXML bindings (curly braces, function bindings, mx:Binding/Observe) easier to write and maintain? AFAIK Not aplicable to curly braces, but yes to <mx:Binding/>. <mx:Binding> has some memory issues not freeing the memory when the container instance is removed from stage (even from memory). The binding never gets removed. http://tech.groups.yahoo.com/group/flexcoders/message/55432 Best X.
