OpenGL attrib_list support

Andreas Hartmetz ahartmetz at gmail.com
Wed Jul 10 09:03:15 PDT 2013


On Wednesday 10 July 2013 15:45:59 Alexander Monakov wrote:
> On Wed, 10 Jul 2013, Andreas Hartmetz wrote:
> > - No support for float-valued attrib_lists because what were they
> > 
> >   thinking, and who uses them anyway?
> 
> Who "they"?  Where can float values in attrib-lists appear?
> 
"they" is Microsoft here - those parameters only seem to occur in WGL.
One example is wglChoosePixelFormatARB with
FLOAT *pfAttribFList, an attrib_list-style parameter with floats.
In addition to an attrib_list-style parameter with ints, mind you, so I
think ~everybody will use the int version anyway.

> > - No support for keys and values in two parallel arrays - I've never
> > 
> >   needed them and they break the basic assumption that each parameter
> >   can be serialized on its own. I may or may not look at implementing
> >   them later.
> 
> Where can such situation arise?

For example
wglGetPixelFormatAttribivARB(..., uint  nAttributes, int *piAttributes,
int *piValues) - the values are out-parameters, but it would still be
nice to interpret them correctly. The required information is now
available as Python data structures in the generator.
Outside of WGL there are similar functions with the difference that one
can only get one attribute value in one call, but it's the same
problem: The return value isn't interpreted correctly.

Andreas


More information about the apitrace mailing list