Hi, As it says in the documentation, the order Component.onCompleted handlers are executed is not defined.
Roughly speaking (as there are exceptions), elements are instantiated from top to bottom, and the onCompleted signals are executed in reverse order of instantiation. But don't rely on that behaviour. Cheers, Aaron On 22/11/2010, at 6:49 PM, ext ext-ivailo.il...@nokia.com<mailto:ext-ivailo.il...@nokia.com> wrote: Hi, as you all know HTML and JavaScript are executed / or evaluated / form the TOP to BOTTOM. So if you have a source of 100 lines it will start from line 1 and will finish with the last one. When you know this you can somehow figure our some tricks you want to make and know what to expect. I have a QML file that I want to trace how it's reacting. Rectangle {onCompleted: {console.col("m1")}} Rectangle {onCompleted: {console.col("m2")}} and in the console output I have m2, m1. so does it mean that in QML we have stack popup priority of structure handling - you parse it from top to bottom and execute it form bottom to top? does it mean that my "later" element will always have Component.onCompleted "before"? Or this reverse order is just temporary or coincidence on my machine or we shall not expect any order of loading - "everything will come when it comes"? Best Regards, Ivo _______________________________________________ Qt-qml mailing list Qt-qml@trolltech.com<mailto:Qt-qml@trolltech.com> http://lists.trolltech.com/mailman/listinfo/qt-qml
_______________________________________________ Qt-qml mailing list Qt-qml@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-qml
