[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] More predictable behavior for !preserveDrawingBuffer

On Mon, Jun 4, 2012 at 4:39 PM, Glenn Maynard <glenn@zewt.org> wrote:
> I started writing this in more depth, but noticed that it might simply not
> be implementable, so I'll just start with a basic description.
> When preserveDrawingBuffer is false, the buffer is cleared when it's
> actually composited.  Would it be possible to clear the buffer as soon as
> the JS code returns to the browser, rather than waiting for compositing, so
> the time of compositing can't affect script behavior?
> This would be efficient with triple-buffering--you just flip the
> backbuffers--but I don't know if that can be done on more restricted
> implementations, especially ES ones.

This question has been raised before; see
for example. Please check the archives, and see if there's new
information or thoughts on topic.


You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl