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
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 i
Looks like the binding for the MyCanvas object is still around. You'll
have to remove the MyCanvas object from the MyComponent object
explicitly. Make sure you've assigned an id to it.
function removeCanvas() {
removeChild(myCanvas);
myCanvas = null; // this is important
}
>From
I have created a minimal flex app to show the problem. You can access
it on
http://www.riapt.org/opensource/removeChildTest/removeChildTest.html.
The source is available (right click-> view source).
As you can see, after creating, destroying and creating again (by
pressing twice the first button)
4 matches
Mail list logo
