Thread: [PyOpenGL-Devel] [ pyopengl-Bugs-557997 ] glCallLists crashes without Numeric
Brought to you by:
mcfletch
Menu
▾
▴
pyopengl-devel
|
From: <no...@so...> - 2002-05-29 18:46:55
|
Bugs item #557997, was opened at 2002-05-19 13:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105988&aid=557997&group_id=5988 Category: GL Group: v2.0 Status: Open Resolution: None Priority: 5 Submitted By: Michael Krause (mkrause) Assigned to: Tarn Weisner Burton (twburton) >Summary: glCallLists crashes without Numeric Initial Comment: I am using PyOpenGL-2.0.0.44.win32-py2.2.exe and had to write this workaround: # The following two lines work with Python2.1, but crash with Python2.2, # so we have to loop over all characters # glListBase(self.fontlist_index) # glCallLists(text) for c in text: glCallList(self.fontlist_index + ord(c)) Is it just me or can anyone verify this? ---------------------------------------------------------------------- >Comment By: Mike C. Fletcher (mcfletch) Date: 2002-05-29 14:46 Message: Logged In: YES user_id=34901 Although Numeric is theoretically optional, I don't think I've tested with a non-Numeric-enabled Python in ages (Tarn may do those tests, however). All of my own code uses vertex arrays and the like, so Numeric is basically a requirement for anything I work with. Suppose the proper thing to do is strip out Numeric and see which tests fail. Will put it on the todo list. ---------------------------------------------------------------------- Comment By: Michael Krause (mkrause) Date: 2002-05-29 14:25 Message: Logged In: YES user_id=22108 After installing Numeric-21.0.win32-py2.2.exe everythings works as expected. I thought Numeric was optional. Rename Numeric.pth to .pth2 to see the crash. The Python2.1 vs 2.2 issue was misleading. 2.1 had Numeric installed on my machine, 2.2 not. Thanks, Michael ---------------------------------------------------------------------- Comment By: Mike C. Fletcher (mcfletch) Date: 2002-05-29 05:24 Message: Logged In: YES user_id=34901 Well, I can't get the sample code (thank-you) to trigger an error. I'm using Python 2.2.1 with the latest PyOpenGL binary distribution for Python 2.2 and wxPython 2.2.3pre3. (This is under Win2K with an ATI Radeon 7500). I can even see the text getting properly displayed. Can you try upgrading to equal versions of each lib to see if that fixes the bug for you? Any other suggestions for replicating the problem? ---------------------------------------------------------------------- Comment By: Mike C. Fletcher (mcfletch) Date: 2002-05-27 06:04 Message: Logged In: YES user_id=34901 Could you give me a piece of sample code that exercises the error? I'll see if I can get my C-coding friend to look at it if I can just pass her a small piece of code that triggers the crash. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105988&aid=557997&group_id=5988 |
|
From: SourceForge.net <no...@so...> - 2003-04-28 09:10:32
|
Bugs item #557997, was opened at 2002-05-19 13:01 Message generated for change (Comment added) made by mcfletch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105988&aid=557997&group_id=5988 Category: GL Group: v2.0 >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Michael Krause (mkrause) >Assigned to: Mike C. Fletcher (mcfletch) Summary: glCallLists crashes without Numeric Initial Comment: I am using PyOpenGL-2.0.0.44.win32-py2.2.exe and had to write this workaround: # The following two lines work with Python2.1, but crash with Python2.2, # so we have to loop over all characters # glListBase(self.fontlist_index) # glCallLists(text) for c in text: glCallList(self.fontlist_index + ord(c)) Is it just me or can anyone verify this? ---------------------------------------------------------------------- >Comment By: Mike C. Fletcher (mcfletch) Date: 2003-04-28 05:10 Message: Logged In: YES user_id=34901 Given the rarity of the error, and the futility of running OpenGL without Numeric, I am marking this closed. 2.0.1 explicitly depends on Numeric, regardless of the internal attempts to recover in those situations where it is absent. ---------------------------------------------------------------------- Comment By: Mike C. Fletcher (mcfletch) Date: 2002-05-29 14:46 Message: Logged In: YES user_id=34901 Although Numeric is theoretically optional, I don't think I've tested with a non-Numeric-enabled Python in ages (Tarn may do those tests, however). All of my own code uses vertex arrays and the like, so Numeric is basically a requirement for anything I work with. Suppose the proper thing to do is strip out Numeric and see which tests fail. Will put it on the todo list. ---------------------------------------------------------------------- Comment By: Michael Krause (mkrause) Date: 2002-05-29 14:25 Message: Logged In: YES user_id=22108 After installing Numeric-21.0.win32-py2.2.exe everythings works as expected. I thought Numeric was optional. Rename Numeric.pth to .pth2 to see the crash. The Python2.1 vs 2.2 issue was misleading. 2.1 had Numeric installed on my machine, 2.2 not. Thanks, Michael ---------------------------------------------------------------------- Comment By: Mike C. Fletcher (mcfletch) Date: 2002-05-29 05:24 Message: Logged In: YES user_id=34901 Well, I can't get the sample code (thank-you) to trigger an error. I'm using Python 2.2.1 with the latest PyOpenGL binary distribution for Python 2.2 and wxPython 2.2.3pre3. (This is under Win2K with an ATI Radeon 7500). I can even see the text getting properly displayed. Can you try upgrading to equal versions of each lib to see if that fixes the bug for you? Any other suggestions for replicating the problem? ---------------------------------------------------------------------- Comment By: Mike C. Fletcher (mcfletch) Date: 2002-05-27 06:04 Message: Logged In: YES user_id=34901 Could you give me a piece of sample code that exercises the error? I'll see if I can get my C-coding friend to look at it if I can just pass her a small piece of code that triggers the crash. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105988&aid=557997&group_id=5988 |
Thanks for helping keep SourceForge clean.
X