[PyOpenGL-Devel] [ pyopengl-Bugs-1959860 ] glReadPixels breaks 2.x compat. breaks pygame.

[SourceForge.net <no...@so...>]

Bugs item #1959860, was opened at 2008-05-07 19:08
Message generated for change (Settings changed) made by mcfletch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105988&aid=1959860&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: v3.0.0
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Mike C. Fletcher (mcfletch)
Summary: glReadPixels breaks 2.x compat.  breaks pygame.

Initial Comment:
Hi,

with glReadPixels changing its interface from 1, 2.x, it breaks pygame.image.save(screen).


This is the only pyopengl function that pygame uses.  

It would be nice if pyopengl 3.x kept the same interface, of returning a string.


cheers,

----------------------------------------------------------------------

>Comment By: Mike C. Fletcher (mcfletch)
Date: 2008-06-06 12:44

Message:
Logged In: YES 
user_id=34901
Originator: NO

Pygame has already changed their code to support PyOpenGL 3.x, the new
version allows the user to specify the data-type they want to have returned
from array-producing code, but at the moment strings are not an option (no
way to generate them in the correct dimensions yet without potentially
falling afoul of the small-string caching mechanisms).

I'm afraid I'll have to mark this "won't fix" as a result.  If you feel
this is a major problem, reopen the ticket and I'll consider it again, but
aside from maybe implementing a "string" output type that could be
selected, I don't see it as a desirable change to make the function always
return strings.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105988&aid=1959860&group_id=5988