Re: [PyOpenGL-Users] problems with glMap1f in pyopengl2
Brought to you by:
mcfletch
From: Mike C. F. <mcf...@ro...> - 2004-03-12 17:40:40
|
Okay, I've confirmed that this is a bug in PyOpenGL 2.0.1.07, and also in CVS. The _PyObject_Dimension(obj0, 1) call is for the wrong object, it should be _PyObject_Dimension(obj3, 1) so that it's taking the size of the array, not the integer constant specifying the size of the array. The problem arose because this code uses the (crufty, evil) d_3_0 SWIG hacks to get the dimension of the array. When doing the SWIG 1.3.13 conversion I tried to find and update all of those hacks to fit the SWIG 1.3.13 version of the hack (argument numbering changed between those versions), but I apparently missed this one. A cleaner mechanism, hopefully, will be available once we transition to SWIG 1.3.21. Anyway, I've checked the (2-character) fix into CVS on both the head (2.0.1 maintenance) and dev-2_1 branches. And now I must get to real work. Have fun, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |