Re: [PyOpenGL-Users] crash on import on Mac OS X after xml-generation merge explained
Brought to you by:
mcfletch
From: Mike C. F. <mcf...@vr...> - 2014-01-28 15:33:04
|
On 14-01-24 04:14 PM, rndblnch wrote: > Mike C. Fletcher <mcfletch <at> vrplumber.com> writes: ... > it does not crash any more. > however on my personal test suite (the same program converted step by step > from using OpenGL 1. to modern OpenGL, see > https://bitbucket.org/rndblnch/opengl-programmable/) it works until the > introduction of vertex attributes (steps 01-direct.py to 06-perpixel.py > work, but 07-attrib.py, 08-pbo.py, etc. give a black screen). > i suspect that the pointer/offset parameter of the glXxxxPointer functions > is not handled properly, i will look into it (i use ctypes arrays, no numpy). I looked into it, and there was, indeed, a problem with the ctypes pointer handling. Basically we were getting pointer-to-pointer (i.e. the address of the pointer variable) instead of the pointer's value when doing a dataPointer() call on them. I've fixed that on bzr head, and all of your samples now seem to run correctly on bzr head. What's weird is that code hadn't changed; it seems that something higher-level meant that the code-path just wasn't being executed in the old PyOpenGL releases. By the way, do you have a tutorial (text) somewhere connected with your samples? And would you like the code linked into the PyOpenGL documentation samples (i.e. when someone looks at the glXxxxPointer functions they'd see a reference to your hg repository?) I fixed an (unrelated) bug that was preventing the various configuration flags (e.g. FULL_LOGGING) from running, and regenerated the OpenGL_accelerate wrappers with the new Cython release. I *think* we're fairly close to a beta-1 release for PyOpenGL 3.1 at this point. I still need to get some time to run the Windows tests and re-run the Linux tests with the updated Cython wrappers. Thanks, Mike -- ________________________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com |