I've done a trace on my application because some private variables were getting null from no-where after the setting routine had run perfectly.
The truth was that the private variable was part of a Mixin, and the setting/getting routines too. But also the constructor, that was the only place where the variable was defined as this.__var = null. Why the Mixim constructor is called at the end of the object construction? When I say "object construction" I'm referring to the constructor of a simple Qooxdoo derived object that calls some Mixin routines while its constructor routine. Let me try to draw it: new Object1-->constructor of Object1 runs-->it runs routines from Mixim1 in the Object1 constructor-->end of Object1 constructor-->Constructor of Mixin1 runs!!! It should be: new Object1 --> constructor of Object1 runs --> constructor of Mixim1 runs--> Object1's constructor continues-->Object1's constructor run routines from Mixim1-->end of Object1's constructor-->done Regards, Herman -- View this message in context: http://qooxdoo.678.n2.nabble.com/Constructor-execution-order-at-Mixin-strange-tp6255774p6255774.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
