Difference between revisions of "User talk:Jgrills"

From OpenGL Wiki
Jump to: navigation, search
(Notice on OpenGL Error)
Line 8: Line 8:
  
 
I am seeing this on Windows, in my case it's happening at shutdown. I did some research and came across this post that seems to describe my issue: https://www.gamedev.net/forums/topic/366057-gl_invalid_operation/
 
I am seeing this on Windows, in my case it's happening at shutdown. I did some research and came across this post that seems to describe my issue: https://www.gamedev.net/forums/topic/366057-gl_invalid_operation/
 +
 +
: The OpenGL specification governs the behavior of the OpenGL system while a functioning, valid OpenGL context is current. That post's code doesn't ''ever'' create an OpenGL context, so the OpenGL specification has nothing to say about its behavior. So the circumstances described by that post are irrelevant to what's supposed to be on this site.
 +
 +
: Now, if you want to qualify your statement with a specific notation that this happens only outside of having a valid OpenGL context made current, that ''might'' be OK. But since pretty much everything on this site starts with that assumption, it seems weird to bring it up only with regard to {{code|glGetError}}. But the current version of the statement suggests that the behavior you describe is permitted by the OpenGL standard or that this behavior is something users should be expect to encounter in normal operating conditions. Neither of these is true (not unless you can find more evidence than a near 15-year-old post that never actually creates an OpenGL context).
 +
 +
: One last thing. When discussing things on a MediaWiki, there's a protocol. You're supposed to use "<nowiki>~~~~</nowiki>" to sign your posts, so that everyone can see who said what. And you're supposed to indent replies with <nowiki>:</nowiki> syntax. [[User:Alfonse|Alfonse]] ([[User talk:Alfonse|talk]]) 04:01, 29 August 2019 (UTC)

Revision as of 04:01, 29 August 2019

Notice on OpenGL Error

You added this notice:

Note that on some platforms in some circumstances, glGetError may return GL_INVALID_OPERATION indefinitely

Such a thing is not really allowed by the OpenGL specification. Implementations cannot indefinitely return errors, so such cases are driver bugs. On which platforms does such behavior happen? Alfonse (talk) 11:45, 28 August 2019 (UTC)

I am seeing this on Windows, in my case it's happening at shutdown. I did some research and came across this post that seems to describe my issue: https://www.gamedev.net/forums/topic/366057-gl_invalid_operation/

The OpenGL specification governs the behavior of the OpenGL system while a functioning, valid OpenGL context is current. That post's code doesn't ever create an OpenGL context, so the OpenGL specification has nothing to say about its behavior. So the circumstances described by that post are irrelevant to what's supposed to be on this site.
Now, if you want to qualify your statement with a specific notation that this happens only outside of having a valid OpenGL context made current, that might be OK. But since pretty much everything on this site starts with that assumption, it seems weird to bring it up only with regard to glGetError. But the current version of the statement suggests that the behavior you describe is permitted by the OpenGL standard or that this behavior is something users should be expect to encounter in normal operating conditions. Neither of these is true (not unless you can find more evidence than a near 15-year-old post that never actually creates an OpenGL context).
One last thing. When discussing things on a MediaWiki, there's a protocol. You're supposed to use "~~~~" to sign your posts, so that everyone can see who said what. And you're supposed to indent replies with : syntax. Alfonse (talk) 04:01, 29 August 2019 (UTC)