Hello,
I noticed a bug in the quartz OpenGL SDL implementation, the
SDL_GL_LoadLibrary function returns 1 for sucessful completion while the
SDL docs indicate that a return value of 0 is the correct return.
–brendan
Yup. Strangely, the SDL_OPENGLBLIT path didn’t catch this error. I
wonder if anyone is checking this result code?
Of course, you realize that this has minimal usefulness on OS X (besides
compatibility) since there is only one OpenGL library on the system. It
should be useful for binding function pointers for extensions, however.
-DOn Mon, 4 Mar 2002, Brendan Burns wrote:
What is the difference between AGL and OpenGL frameworks on OS X?On Monday, March 4, 2002, at 09:37 PM, Darrell Walisser wrote:
On Mon, 4 Mar 2002, Brendan Burns wrote:
Hello,
I noticed a bug in the quartz OpenGL SDL implementation, the
SDL_GL_LoadLibrary function returns 1 for sucessful completion while
the
SDL docs indicate that a return value of 0 is the correct return.
–brendan
Yup. Strangely, the SDL_OPENGLBLIT path didn’t catch this error. I
wonder if anyone is checking this result code?
Of course, you realize that this has minimal usefulness on OS X (besides
compatibility) since there is only one OpenGL library on the system. It
should be useful for binding function pointers for extensions, however.
-D
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
What is the difference between AGL and OpenGL frameworks on OS X?
AGL (Apple GL) seems to be for Carbon applications. NSOpenGL is for
Cocoa, CGL (Core GL) is for whatever. We are using both NSOpenGL and CGL
in SDL at the moment. We might have to borrow some things from AGL to
complete the implementation (see QZ_GL_GetAttribute()).
Cheers,
DarrellOn Mon, 4 Mar 2002, David Leimbach wrote:
On Monday, March 4, 2002, at 09:37 PM, Darrell Walisser wrote: