GetIntegerv is an interesting example because it can be passed a pointer to a scalar or to an array, depending on the state being queried. I'd think depending on the language, if you were returning a...
Type: Posts; User: Jon Leech (oddhack)
GetIntegerv is an interesting example because it can be passed a pointer to a scalar or to an array, depending on the state being queried. I'd think depending on the language, if you were returning a...
Alfonse captured a bunch of the things I'd have said had I been online earlier, but here are a few additional comments.
The goal of doing this wasn't to deprive people of things they're used to,...
The "actual documentation" is more complete (and prettier) now: see PDF
The old gl.spec & related files are being retired, replaced by an XML-based description of the GL, GLX, WGL, GL ES, and EGL APIs as has been promised since slightly before the Dark Ages. The XML...
We've opened up the directories containing GLSL (manglsl/) and common utility files (mancommon/) for anonymous SVN access as well - sorry for the oversight. The first post in this thread has been...
The EGL context creation API has functionality defined for both GL and ES contexts, but most implementations of EGL exist on mobile devices where only OpenGL ES is available. There is an EGL (1.1, I...
So maybe a baseball cap with the quick ref guide printed on it? :-)
Yes. You cannot expect that the static entry points for anything in glext.h will be defined in the GL link library, in which case there's no utility in defining a bunch of prototypes for functions...
You can do that, but as previously noted, nothing is deprecated from the compatibility profile, so a forward-compatible compatibility profile is exactly the same thing as a non-FC CP :-)
I would...
They overlap but the use cases are very different. The FC context is really only intended as a futureproofing aid for developers, along the lines of the (otherwise so-far mythical) "debug context"....
To speak somewhat in our own defense, the GL and GLSL specs are huge, complex documents that go through many, many revisions during the process of creating a new version. John and I try to keep the...
Well, we kinda had to introduce an enabling mechanism to select the profile, once we introduced profiles. If you don't specify a profile or version or context flags in the attribute list, then...
OK, I understand now. I think both Sun and Apple have done vendor extensions along these lines, and we have sometimes discussed it as a future use case in the ARB. If we do something like this in a...
We folded the profile extension into the same documents as the original create_context extensions, largely because it was necessary to get them out on time for SIGGRAPH, for arcane reasons involving...
I'm not certain what you're asking, but if it is whether we would make sync objects affect the behavior of previously existing API calls, there are no plans to do that. BufferData in GL 3.2 does just...
There's a draft <GL3/gl3.h> header in the Registry now, as described in appendix H.2 of the OpenGL 3.1 specification. This is not ready for general use yet, but we'd appreciate feedback from...
Recently there's been a problem with viewing the online man pages in Internet Explorer, due to the W3C banning IE from accessing a DTD referred to by each man page. Without going into a long...
SGI has updated their FreeB license, which applies to many of the man pages Khronos distributes. Version 2.0 of FreeB is just an X11/MIT-style license.
This doesn't have any substantive effect on...
GLint n, i;
glGetIntegerv(GL_NUM_EXTENSIONS, &n);
for (i = 0; i < n; i++) {
printf("%s\n", glGetStringi(GL_EXTENSIONS, i);
}
glGetString() is not deprecated, only the GL_EXTENSIONS...
12-ML-47978-ML-
Moved to "Items of Importance" folder now that I can post there.
Khronos has released the OpenGL man page XML sources. This was done mostly at the request of people wishing to adapt the man pages to other output formats or language bindings.
You will need to...
They do. Same mechanism although the APIs are partitioned a bit differently with just the original core API entry points in glx.spec/wgl.spec and the extensions in {glx,wgl}ext.spec.
I set things...
The first field is for the parameter "direction" (in, out, in/out) and the second the "transfer type" (array, reference, value). This could potentially be used together with parameter type...
I'm not sure how you mean "kept". The spec files are the actual registry for GL commands and tokens, and they get updated when there's something new to put in them. Usually updates will lag new core...
Sorry I can't quickly find the spot in the SDK thread in which this came up, but I've just updated the public Registry with a glext.h and accompanying gl.spec / enumext.spec files defining the 3.0...