On Wednesday 06 February 2008 11:44:58 am you wrote: > Chris Robinson wrote: > > I don't think it's correct to add this since it's not supported (the > > extension string isn't exported and it can't be easilly emulated). If an > > app is trying to set that attribute without the extension being > > advertised, I'd say the app is broken. If you're intending on adding > > support, you may want to familiarize yourself with how wine emulates > > render_to_texture and look over the extension: > > http://opengl.org/registry/specs/NV/render_depth_texture.txt > > "I don't think it's correct to add this since it's not supported" > The > > case WGL_BIND_TO_TEXTURE_RGB_ARB: > case WGL_BIND_TO_TEXTURE_RGBA_ARB: > case WGL_BIND_TO_TEXTURE_RECTANGLE_FLOAT_R_NV: > are not supported either. The WGL_BIND_TO_TEXTURE_DEPTH_NV came up as a > fixme since it isn't in the switch.
The formats are supported in X11DRV_wglGetPixelFormatAttribivARB, X11DRV_wglCreatePbufferARB and the other render-to-texture functions, and the render-to-texture extension is advertised.. There's just nothing to do in that function for them since the hint will always be accepted. But I don't see the point in supporting a pbuffer creation hint that an app shouldn't be using without the extension being advertised (actually, I think pbuffer creation is supposed to fail if an unsupported attribute is specified). Which app is trying to use it? > Again, just trying to learn, not annoy > people with tiny fixes. No annoyance to me, just explaining why I don't think it's something to handle. :)