[PyOpenGL-Users] Anyone feel like looking up glGet constant return sizes?
Brought to you by:
mcfletch
From: Mike C. F. <mcf...@vr...> - 2014-04-02 14:35:46
|
One of the things that PyOpenGL does when you call GL's glGet* family of functions is to auto-allocate the return array. It does this with a (manually maintained) mapping from enum/constant -> array-dimensions which is defined in src/glgetsizes.csv in the source tree. I have fallen *way* behind in keeping up with this list, so there are currently 54 known glGet-capable constants that don't have a defined size (there are *other* constants that should be mapped I'm sure, but only those constants which show up in a formal extension description on OpenGL.org actually get automatically recognized as ones to annotate). The work is mostly mechanical, you have to look up the constant, find the spec, read through it to see what is expected when you do glGet* for that constant, and determine what the array shape should be. Most of the glGet operations return a single value, but every once in a while you'll find one that returns an array, a string, etc. If anyone feels like hunting down some of those constants and sending me a ping with their values, that would be great. If you felt like checking out the source, doing a few dozen, and sending a bzr patch, that would be even nicer. The fact that I've fallen so far behind was brought to my attention by the fact that the constants for the various debug extensions were not properly mapped in glGet, so you had to manually pass in the data arrays to do any debug extension work. Enjoy, Mike -- ________________________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com |