>I believe you're trying to concat two models.

I'm not, I just trying to fix a bug that was not on previews release ;)
My playground example is clear, his only purpose is to show you the bug but
the code has nothing to do with our real code. Of course I can add a
if(model === null) {return;} but I don't see any reason to not change the
actions order like on the patch provided. If you compare the controller list
on 1.2 and 1.3 you will see that this part of the code have been all
rewrited and the more likely it is that this bug was added accidentaly. Do
you see a reason to bind the model after the label ? Do you see a reason to
call the label option with no model ?

Thank you,
David
-- 
View this message in context: 
http://qooxdoo.678.n2.nabble.com/controler-list-bug-on-new-version-tp5888163p5889657.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to