On Mon, 2011-05-30 at 16:15 +0100, Andrew Flegg wrote:
> BTW, list handling in QML is a pain. I suspect this list
> recreation/parsing/manipulation is accounting for a large portion of
> the CPU usage. Other thoughts from Qt Quick experts appreciated; but
> the graphical performance is orders of ma
On Mon, May 30, 2011 at 6:15 PM, Andrew Flegg wrote:
> BTW, list handling in QML is a pain. I suspect this list
> recreation/parsing/manipulation is accounting for a large portion of
> the CPU usage. Other thoughts from Qt Quick experts appreciated; but
Have you considered using plain javascript
On Mon, May 30, 2011 at 16:07, Ville M. Vainio wrote:
>
> Right - so I confirmed Andrew's fear [was unnecessary] that QML would
> be "stupid" about this, and waking up the process when it should be
> steady (e.g. by doing a dummy op at 60fps).
Thanks.
> If you have animations that proceed when t
On Mon, May 30, 2011 at 6:07 PM, Ville M. Vainio wrote:
> Right - so I confirmed Andrew's fear that QML would be "stupid" about
Erk, reverse logic, I confirmed Andrew's fear was *unnecessary*, of course.
___
maemo-developers mailing list
maemo-develope
On Mon, May 30, 2011 at 5:49 PM, Robin Burchell wrote:
>> I confirmed that e.g. QmlReddit does nothing when it's hidden.
>
> Note that of course, nothing will be happening if there's nothing to
> actually happen. If your objects aren't moving, etc, then Qt won't
> constantly have to redraw items,
On Mon, May 30, 2011 at 15:56, Thomas Perl wrote:
>
> For anyone that's interested in how it's done (feedback and
> improvement suggestions welcome!), you can find the patch against
> Attitude here:
>
> http://thp.io/2011/maemo/attitude_activemonitor.patch
...and now here:
http://gitorious.
Hi Andrew,
2011/5/30 Andrew Flegg :
> Qt Quick 1.1 apparently features a "Qt.application.active" read-only
> property[1] which can be connected (somehow) to stopping animations,
> reading sensors and so on.
> [...]
> Thoughts welcome. To be honest, it's amazing (and disappointing) that
> there isn
On 30/05/11 15:46, Ville M. Vainio wrote:
On Mon, May 30, 2011 at 4:55 PM, Andrew Flegg wrote:
Thoughts welcome. To be honest, it's amazing (and disappointing) that
there isn't a way of doing this in Qt Quick 1.0. Can anyone confirm
whether or not it's at least not updating the screen when hid
On Mon, May 30, 2011 at 4:55 PM, Andrew Flegg wrote:
> Thoughts welcome. To be honest, it's amazing (and disappointing) that
> there isn't a way of doing this in Qt Quick 1.0. Can anyone confirm
> whether or not it's at least not updating the screen when hidden (it
> does in the task manager), an
On 30/05/11 15:23, Cornelius Hald wrote:
The 50%-60% CPU is the new QML implementation? Sounds a bit much, maybe
you need to enable OpenGL for drawing?
An easy approach to test that:
QDeclarativeView view;
view.setViewport(new QGLWidget);
--
Robin Burchell
http://rburchell.com
___
Hi Andrew,
I can't answer all of this, but I'll give it a try anyways :)
On Mon, 2011-05-30 at 14:55 +0100, Andrew Flegg wrote:
> Qt Quick 1.1 apparently features a "Qt.application.active" read-only
> property[1] which can be connected (somehow) to stopping animations,
> reading sensors and so on
Hi,
Qt Quick 1.1 apparently features a "Qt.application.active" read-only
property[1] which can be connected (somehow) to stopping animations,
reading sensors and so on.
However, in my rewrite of Attitude[2] in QML, I'd like to do something
similar. In fact, given my app's running at 50-60% CPU, I
12 matches
Mail list logo
