<br><br><div><span class="gmail_quote">On 4/18/07, <b class="gmail_sendername">IOhannes m zmoelnig</b> <<a href="mailto:zmoelnig@iem.at" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">zmoelnig@iem.at
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
it would take some work to not only use the GLEW functions stubs but<br>also to check whether the calls are supported; i guess this work is<br>rather easy but dull</blockquote><div><br>It would take a long time to put GLEW checks in every object that uses GL, but that is probably not needed. Starting with the most troublesome objects like the shader and texturing objects would be less work but the results would be incomplete.
<br><br>The big problem I found with GLEW is that, on Windows at least, it requires a working window context in order to return the correct info. The assumption appears to be that you only use OpenGL for games and the first thing your game does is take complete control of the computer and put a fullscreen context up. You are writing a game right? Any checks I put in GemMan were worthless and so are checks in the object constructors. That limits the usefulness of GLEW although a check in startRender() can work for certain features.
<br></div><br></div><br>