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

Re: [Public WebGL] Changing context attributes

We should get this 'for free' with the new DrawingBuffer stuff from the WebGL-in-Workers work.


----- Original Message -----
From: "Bill Baxter" <wbaxter@google.com>
To: "public webgl" <public_webgl@khronos.org>
Sent: Friday, September 20, 2013 11:52:48 AM
Subject: [Public WebGL] Changing context attributes

How difficult would it be for WebGL implementations to allow changing
context attributes on the fly?
There are some attributes like preserveDrawingBuffer or antialias that can
be expensive on some machines.  It's hard to determine ahead of time which
machines those are with the info available to javascript apps.  So it would
be nice to be able to turn off multisampling in mid-stream to see if that
made things better for a user.

Well-written applications already have to deal with context loss, so
changing the attributes could just trigger a context loss.

Without this, it seems that an app has no recourse but to tear down the
whole Canvas and restart everything, which may be difficult given that many
parts of the app may have access to the Canvas.  (At the very least they
have access to it via the .canvas property of the webgl context).

Any thoughts?


Bill Baxter | Software Engineer | wbaxter@google.com | eat more peas!

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