[Qt-qml] Timer without animation ?

[Gregory Schlomoff]

> 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.

Hmm, there must be some kind of misunderstanding here... I gave you an
in-depth explanation of why putting a Timer element inside a QtObject
doesn't work if you try to do it the standard way, and how to make it
work.

I even went as far as testing the code on my machine before answering
to your mail.

Have you read my original mail ?


On Mon, Jan 10, 2011 at 6:14 PM,  <petrus.lundqvist at nokia.com> 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.
>
> Peppe
>
> ________________________________________
> From: qt-qml-bounces+petrus.lundqvist=nokia.com at qt.nokia.com [qt-qml-bounces+petrus.lundqvist=nokia.com at qt.nokia.com] on behalf of ext Gregory Schlomoff [gregory.schlomoff at gmail.com]
> Sent: Monday, January 10, 2011 12:56
> To: Alpert Alan (Nokia-MS-Qt/Brisbane)
> Cc: qt-qml at qt.nokia.com
> Subject: Re: [Qt-qml] Timer without animation ?
>
> Edit:  my answer was based on the fact that you wanted to use QtQuick,
> but for some unknown reason, didn't want to use visual elements (ie:
> elements inherited from Item).
>
> If you want a real GUI-less approach, then Alan's suggestion is the
> way to go: create your own set of QObject-derived classes, and use
> them from QML, and do not use the QtQuick module.
>
>
> On Mon, Jan 10, 2011 at 5:47 PM, Alan Alpert <alan.alpert at nokia.com> wrote:
>> On Monday, January 10, 2011 08:05:26 pm ext Attila Csipa wrote:
>>> Is it possible to have a Timer without having a visual item that brings in
>>> the animation timer ? Think
>>>
>>> QtObject {
>>>     Component.onCompleted: console.log("hello world");
>>>     Timer {
>>>              interval: 500; running: true; repeat: true;
>>>              onTriggered: console.log("tick");
>>>     }
>>> }
>>>
>>> This gives somewhat cryptic Component is not ready error, but does work if
>>> I replace QtObject with Item. Now, you will be asking well, why don't you
>>> just use Item, and the answer is that it feels a bit weird - I'm
>>> experimenting with GUIless QML (think custom structured QtObject creation,
>>> textual UIs, etc).
>>>
>>
>> Timer is part of the QtQuick module, and that entire module is designed for
>> GUI creation. If you don't want a GUI, but want to use QML, then just don't
>> import the QtQuick module and use items from elsewhere. An example of this is
>> that .qmlproject files import the QmlProject module to store the project
>> description in QML, entirely GUI-less.
>>
>> 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.
>>
>> --
>> Alan Alpert
>> Software Engineer
>> Nokia, Qt Development Frameworks
>> _______________________________________________
>> Qt-qml mailing list
>> Qt-qml at qt.nokia.com
>> http://lists.qt.nokia.com/mailman/listinfo/qt-qml
>>
> _______________________________________________
> Qt-qml mailing list
> Qt-qml at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt-qml
>