Hi All,
I've subclassed qx.data.controller.Form and i've added this destructor:
//////////////////////
},destruct:function(){
//////////////////////
this.setModel( null );
this.setTarget( null );
That seems to fix all he problems.
Because it tears down all the bindings.
I think this is a bug, because the bindings are setup by the controller and
when the controller is disposed, the bindings need to go as well.
In my case the target has been disposed, but even if both continue to exist,
the bindings need to go when the controller goes.
Right?
The bindings are clearly managed by the controller, because changing either
the model or the target properties tears down the bindings as well.
Perhaps I don't need both calls in the destructor, either one would destroy
the binding, but it feels more 'orthogonal' and 'future-proof'.
-- Met vriendelijke groeten,
-- Ralf ( @ gong.nl // **** )
2010/7/17 Ralf Nieuwenhuijsen <[email protected]>:
> Hi All,
>
> It seems that it has no destructor code that removes the bindings?
> So, when I tear down the form, but not the model, I get errors.
> I've tried to remove the binding manually. But it seems the bindings
> are recursive as well? Likely directly between the fields and the
> form-elements?
>
> -- Met vriendelijke groeten,
> -- Ralf ( @ gong.nl // **** )
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
