QPropertyAnimation doing nothing

SGaist

Hi,

You're allocating it on the stack, so as soon as your function is done, animation is destroyed.

McLion

@SGaist
I realized that later and I was just about to update this thread.
I now have in the constructor of the main window and in the header, class private section:

QPropertyAnimation *animation;

And changed the rest to:

animation = new QPropertyAnimation(ui->webGUI, "geometry");
animation->setDuration(10000);
animation->setStartValue(QRect(0, 0, 100, 30));
animation->setEndValue(QRect(x, y, w, h));
animation->start();

Still no joy!
There's still something wrong.

SGaist

You should rather start that animation once everything is constructed using e.g. a single shot QTimer with value 0. Right now you are starting your animation while the event loop hasn't even started.

McLion

I'm not sure I understand you correctly. This part of the code

animation = new QPropertyAnimation(ui->webGUI, "geometry");
animation->setDuration(10000);
animation->setStartValue(QRect(0, 0, 100, 30));
animation->setEndValue(QRect(x, y, w, h));
animation->start();

is in an function that is called normally at runtime when everything is up and running.

SGaist

Is webGui in a layout ?

McLion

No. I have the following structure:
-- QTGUI_MainWindow (class QMainWindwo)
--- centralWidget (class QWidget)
---- webGUI (class QWebView)
---- ...... all other elements

McLion

Got it working.
Silly (and embarrassing) bug in correct calling ...

Thanks anyway!

McLion

I'd like to open this again.
Is this known to be extremely power consuming?
Animating a Textbox or an empty WebView works acceptable.
If it's loaded with some html content it's extremely choppy, not to say unusable.

SGaist

It depends on what you are currently animating. If it something that needs processing before painting then you might get a performance hit.

McLion

OK. I changed the code to make sure there is nothing else consuming CPU power while moving. Still, specially when moving fast, edges are jagged while moving and sometimes it even jumps.

Could be the limit of the ARM CPU or the directFB graphic acceleration.
It would be better if supplying new coordinates to the FB would be synced to the frame rate, but I don't think that I can change something on that level.

Too bad ..