OK, fair to avoid such long discussion again and make it llittle bit mode
educative, but also just to summary the available options to
overload/workaround the Mixin loading:
.- Using qx.Class.include() can "force" the Mixin to be loaded at that point
and not at the end of the current order ?
.- Use a defer:
defer: function(statics,members,properties){
members.setContextMenuHandler(0,members.__handler);
}
.- Use a timer:
qx.util.TimerManager.getInstance().start(
function(userData, timerId)
0, this, null, 1);
}
(well, get the idea, because the code looks bad in syntax)
Am I ok?
Regards,
Herman
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Constructor-execution-order-with-Mixin-strange-tp6255774p6256210.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
