summaryrefslogtreecommitdiff
path: root/src/mesa/main/context.c
diff options
context:
space:
mode:
authorRoland Scheidegger <sroland@tungstengraphics.com>2007-07-18 18:07:12 +0200
committerRoland Scheidegger <sroland@tungstengraphics.com>2007-07-19 17:59:31 +0200
commit6075df53b5435ddada989d776d989132def363a6 (patch)
tree61bb3521d9677d6b387e3ecfdb9465242466ecd9 /src/mesa/main/context.c
parentf9ac01eac511aa9ea0b8b48774022a08d0fc2f3b (diff)
more fixes for mesa's fbo handling (fixes tests/fbotest1/2)
Diffstat (limited to 'src/mesa/main/context.c')
-rw-r--r--src/mesa/main/context.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/mesa/main/context.c b/src/mesa/main/context.c
index 2ad1badac7..4e6732dc7a 100644
--- a/src/mesa/main/context.c
+++ b/src/mesa/main/context.c
@@ -1499,6 +1499,11 @@ _mesa_make_current( GLcontext *newCtx, GLframebuffer *drawBuffer,
if the DRIdrawable changes, and someone may rely on them.
*/
/* What a mess!?! */
+ /* XXX this is still not quite correct. Imagine a user-created fbo
+ bound on a context. Now rebind with a completely new drawable.
+ Upon rebinding to the window-framebuffer, we have no idea what
+ the read and write buffers should be (front, back, ...) - that
+ information was only available in the previously used drawable... */
int i;
GLenum buffers[MAX_DRAW_BUFFERS];
for(i = 0; i < newCtx->Const.MaxDrawBuffers; i++) {