Hi Charley,
In what fashion are you using your animation? I'm asking that because in
Quick you can use animations in several ways, to name a few:
- Inside a Behavior
- Inside a Transition
- As a stand-alone element you explicitly call start and stop
- As an event handler onClicked: Animation { blah }
What you mentioned can be a bug, so please provide us with a little bit more
info on how are you using it, IOW, where are you writing MyParallelAnimation
{} ?
WRT to the base class of animations, no, they are just plain QObjects, not
QDeclarativeItems. The latter is reserved for types that belong to the scene
graph, and potentially do painting, while the former is for support objects
like animations, states, etc.
Cheers,
Eduardo
On Wed, Nov 3, 2010 at 9:53 AM, Charley Bay <charleyb...@gmail.com> wrote:
> >From the QML docs, it appears the pause/resume and start/stop properties
> for Animation elements are related (setting one influences the other), and I
> appreciate the (helpful) messages in the "console.log()" from within the QML
> libraries when you attempt to "resume" an animation that was not previously
> paused, or "pause" an animation that is currently stopped (that's nice).
>
> I'm creating a ParallelAnimation with a few nested SequentialAnimations as
> a top-level QML element (e.g., in its on "MyParallelAnimation.qml"). It
> works fine.
>
> However, I can't seem to pause or stop this thing, whether done
> declaratively with "paused/running" or imperatively with "stop()/pause()".
> It just keeps trucking like the Energizer Bunny. Does anyone have an
> example of doing this (with a ParallelAnimation in its own file?)
>
> The properties are set and the calls are made -- it just won't stop/pause.
> After setting the property or performing the call, I can "read" the value
> from within the Animation element, and yes, they are correctly set to
> "paused: true" or "running: false". However, the animation keeps running
> (launched through QDeclarativeView from C++). (I *did* set "loops:
> Animation.Infinite", but don't set "alwaysRunToEnd:")
>
> Further, (question) are animations "special" (e.g., apparently not derived
> from Item{}, they don't appear to have a corresponding QDeclarativeItem)?
> For example, are there rules or considerations to using an Animation as a
> generic QML Element anywhere you might otherwise use a QML Item{}-derived
> element? (I've made some interesting observations on this, mostly related
> to what properties that apparently cannot be "bound" within an Animation in
> certain situations, and I'm unsure of which parts of my observations are
> "expected" or "anomalous".)
>
> Thanks!
>
> --charley
>
>
> _______________________________________________
> Qt-qml mailing list
> Qt-qml@trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-qml
>
>
--
Eduardo M. Fleury
OpenBossa - INdT
http://eduardofleury.com/
http://www.openbossa.org/
_______________________________________________
Qt-qml mailing list
Qt-qml@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-qml
