- From: Charles Iliya Krempeaux <supercanadian@gmail.com>
- Date: Mon, 13 Jun 2005 18:22:13 -0700
Hello,
On 6/13/05, Sjoerd Visscher <sjoerd at w3future.com> wrote:
> Charles Iliya Krempeaux wrote:
> > IMO, it would be better to a have solution to this built into the API.
> > Maybe with some kind of "drawing transaction".
> >
> > (A "draw transaction" is a little higher level than "double
> > buffering", and allows you use other systems for this, other than
> > "double buffering". And would probably be safer, considering much of
> > JavaScript is done via events.)
>
> This isn't needed. Just like in normal HTML a drawing transaction is
> automatically started when the javascript code starts, and finished when
> the javascript code is done. And this is how it is implemented in
> Firefox (don't know about Safari).
>
> Maybe the spec should describe this somewhere? Not specifically for
> canvas, but for script in general: Changes on the DOM must be performed
> instantly, and values like offsetWidth etc. must be recalculated, but
> only visible when the script is done.
Yes, please do :-) (It wasn't obvious to me.)
See ya
--
Charles Iliya Krempeaux, B.Sc.
charles @ reptile.ca
supercanadian @ gmail.com
developer weblog: http://ChangeLog.ca/
___________________________________________________________________________
Ask the toughest Linux System questions at... http://linuxmanagers.org/
Received on Monday, 13 June 2005 18:22:13 UTC