At the moment, yes, it looks like you have to remove *every* object with a binding on it explicitly or the binding still remains in the background (and the setter keeps getting called). This is definitely a bug in the Flex framework. (Probably someone from Adobe should log it using your standalone test files.)
I don't know if there's a practice for getting around this behaviour (bug). I'll look at it tomorrow and try to come up with a more simple workaround than having to remove every object like that. On 4/23/07, João <[EMAIL PROTECTED]> wrote: > Great!!! It works as a charm > > So, for every component i want to remove, i need to make sure that i > remove also sub-components with bindings, right? Is there an easier > way to achieve this? I have several views being added or removed by > addChild or removeChild, each one of them it a lot of bindings inside. > Is there a practice adviced for this? > > Thanks, > > > João Saleiro > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > >
