Bugs item #1498439, was opened at 2006-05-31 19:27
Message generated for change (Comment added) made by illume
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105988&aid=1498439&group_id=5988
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: GL
Group: v2.0.1
>Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Mike C. Fletcher (mcfletch)
Summary: glTexImage1/2/3D does not allow NULL texture data
Initial Comment:
The glTexImage1/2/3D calls do not allow NULL texture
data to be passed in. For example, the following
valid OpenGL call fails with a TypeError:
glTexImage2D(GL_TEXTURE_2D, 0, GL_RGB8, 512, 512, 0,
GL_RGB, GL_INT, None)
File "gl.pyx", line 592, in gl.glTexImage2D
TypeError: expected string or Unicode object,
NoneType found
A NULL texture is useful when you want to create a
render target texture or a texture whose content will
be defined at a later time.
Regards,
Sami Kyöstilä <sky...@TH...>
----------------------------------------------------------------------
>Comment By: Rene Dudfield (illume)
Date: 2008-01-23 01:10
Message:
Logged In: YES
user_id=2042
Originator: NO
What about allowing the use of 0?
Often in example opengl code 0 is used, and not NULL. Passing in 0
currently fails - where I think it should act as C opengl does. This would
allow more copy/paste examples to work from C code.
cu,
----------------------------------------------------------------------
Comment By: Mike C. Fletcher (mcfletch)
Date: 2008-01-20 03:04
Message:
Logged In: YES
user_id=34901
Originator: NO
This is now working in 3.x CVS.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105988&aid=1498439&group_id=5988
|
