[Qt-interest] Strange GL profile behaviour

[Yves Bailly]

Sean Harmer a écrit :
> On Tuesday 19 April 2011 08:31:27 Yves Bailly wrote:
>> Hello all,
>> While trying to do some core profile (3.2) OpenGL, I see something a bit
>> strange. All of this on Windows 7 64bits, same result using Visual C++ or
> [...]
> Take a look at this thread:
> http://developer.qt.nokia.com/forums/viewthread/4856/
> Short story is, Qt's support for resolving GL entry points was broken when 
> using Core Profile (due to using glGetString() rather than glGetIntv() and 
> glGetStringi()). This is now fixed in git master so you can either use git-
> master or just use the Compatibility profile for now.

Well, that doesn't explain the weird behaviour... after creating a context
through a QGLPixelBuffer, I get a nice Core 3.3 profile, while after creating
a context through a QGLWidget, I get a 2.1.2 profile... even when asking for
QGLFormat::CompatibilityProfile as default format.

Even stranger, some functions are not resolved in the second case, e.g.
"glBindBufferBase" is fine in the "pixel buffer" context, but not available
in the "gl widget" context. I've added a workaround to keep the functions
address before creating the QGLWidget, but that's not satisfactory at all
(I'm using the latest Glew available, by the way).

Is "git-master" stable enough to be used?

Regards,

-- 
      /- Yves Bailly - Software developper  -\
      \- Sescoi R&D  - http://www.sescoi.fr -/
"The possible is done. The impossible is being done. For miracles,
thanks to allow a little delay."