On Monday, January 10, 2011 09:14:36 pm Petrus wrote: > I don't think you really answered the question though. The original > question is why the Timer element only works in Item but not with QtObject > -based parents. It's a perfectly valid question as you might use QtObject > -based parents for various things and want to have timers in them. Just > because QML is for UI's doesn't mean that there aren't non-visual elements > as part of the big picture. Models and model items are good examples of > this. > > > Since non-GUI modules are not common yet, this means that you may have to > > write your own Timer element which does not synchronize with the > > animation Timer. > >
I hinted at it there, but more clearly put the QtQuick Timer is GUI oriented because it synchronizes with the animation timer. It "can" be used GUI-less but, like the models in QtQuick as well, it is specifically designed for use in GUI creation. The big-picture of using QML in non-UI situations will involve not basing it off the Qt UI Creation Kit module. -- Alan Alpert Software Engineer Nokia, Qt Development Frameworks _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
