Got it. Thanks for the explanation. At the very end I used a simle workaround: because the constructor on Mixin was only used for creating the private variables, I've modified the rest of the Mixin code (not much, it's a mixin after all!) to assume that it can happen that the property does not exist, so it get creates an reseted everytime this case happens.
It's a little bit more of code, but I avoid the constructor on the Mixin. Yes, I agree that Mixins are very powerful but dangerous. Even with that,it's a great idea for code reusing. Regards, Herman -- View this message in context: http://qooxdoo.678.n2.nabble.com/Constructor-execution-order-with-Mixin-strange-tp6255774p6260917.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
