Hello Sebastian,
thanks for the reply.
I sent another mail yesterday evening but it seems that it got lost somehow.
Anyway, I tried to do what you suggested and came up with the following
code:
someButton.addEventListener( "execute", function intenseEvent(e) {
blockPlane.set({ width:3000, height:3000 });
qx.client.Timer.once(function() {
// processor intensive part
blockPlane.set({ width:0, height:0 });
}, this, 500
});
and it is working like a charm. :)
Do you have any suggestions as to how low I can safely set the timer
value without getting any weird and unexpected results? I have a quite
fast machine here for testing, other people will most likely have much
slower systems when the application goes live.
Regards,
Daniel Haferkorn
Sebastian Werner wrote:
> Daniel,
>
> this is a browser issue. You cannot update a style and running a CPU
> intensive method after it. The result is that the browser will update
> the display after the execution of this method. A common workaround is
> to execute the (processor intensive) method in a timeout e.g.
> qx.client.Timer.once(...)
>
> Sebastian
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
