Thread: [PyOpenGL-Users] TexImage3D commented out?
Brought to you by:
mcfletch
From: Nathaniel F. <th...@cm...> - 2006-01-25 14:39:37
|
Hi, My basic question is about getting glTexImage3D working. The rest of this email is a detailed account of my attempt to get it working, but it seems so deliberately disabled that I wonder if I'm missing something simple. So feel free to straighten me out if I'm on the wrong track! Or if I should just submit a patch and get over it, let me know that too. It sort of feels like PyOpenGL is only meant to support OpenGL 1.1 -- which seems a little out of date. Cheers, Nathaniel ---- Ok, glTexImage3D, glDrawRangeElements, and a bunch of other calls are mentioned in the documentation, but they are commented out (/* ... */) of GL__init__.i in both releases, and in the CVS repository. Not only that, they are behind #ifdef API_VERSION_WORD >= 258 Which has two problems: the real define is API_VERSION, and it is only set to 256 and 257 (#BUILD api_versions [0x100, 0x101]) Finally, once I uncommented the calls, and changed API_VERSION_WORD to API_VERSION, and added 0x102 to the build versions, there were missing semicolons (and an extra '%{'). And then, there appears to be problems with the swig magic that knows what to do with variables like d_4_0 and n_3, etc. So I commented out all the smart python variants and just went with the vanilla versions. Now everything seems to compile... but everything still seems a little rinky-dink. For example, GL_TEXTURE_3D isn't defined because of some funny business in GL__init__.i, and so I have to import GL.EXT.texture3D and use GL_TEXTURE_3D_EXT. I should note that glInitTexture3DEXT() never ever returns 1, even though both my Mac and Linux box obviously support 3D textures. So... is there a good reason that all this was turned off five different ways, or was it an oversight? |