Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
5.3.0 Beta1
-
None
-
Win 8.1 x64, VS2013, OpenGL
Description
Calling QOpenGLTexture.destroy(), or deleting a QOpenGLTexture object if no texture was actually created triggers an unwanted warning:
"Requires a valid current OpenGL context.
Texture has not been destroyed"
The problem has nothing to do with the OpenGL contex, and we should be able to destroy multiple times or delete the object (without an actual texture being created) without getting this warning.