I don't think there is a way to know when the engine is 'idle'. The engine itself doesn't know anything about the layouting code.
What exactly are you trying to do? Maybe we can suggest alternatives. Girish On Tue, Oct 11, 2011 at 11:40 AM, Kauppi Sauli (Nokia-MS/Helsinki) <[email protected]> wrote: > Hi, > > It would be useful to also know which is the best way to generally > notice that declarative engine has become to idle state? > > In my case (described in previous mail below) Timer with interval 0 does > not seem to be working. And I would rather not use Timer anyway. > > Thanks, > Sauli > > On 10/10/2011 09:08 AM, ext Kauppi Sauli (Nokia-MS/Helsinki) wrote: >> Hi, >> >> Qt-components provides Window element for applications: >> https://qt.gitorious.org/qt-components/qt-components/blobs/master/src/meego/Window.qml >> >> I need to know when re-layouting of Window's child elements has >> completed, after window area is changed during orientation change. >> >> I know when orientation changes (based on SIP/VKB area change). But >> after this, how can I get indication when re-layouting has been completed? >> >> It is not enough to observe changes on Window's property values, as >> Window's child elements' property values area still changed after >> Window's property values are changed (because of anchors and property >> bindings). >> >> Thanks, >> Sauli >> >> _______________________________________________ >> Qt-qml mailing list >> [email protected] >> http://lists.qt.nokia.com/mailman/listinfo/qt-qml >> > _______________________________________________ > Qt-qml mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-qml > _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
