This wraps the GL4 instance in DebugGL4 when the plugin is turned on while debug logging is enabled, if it is present on the classpath. When launching HD through HdPluginTest, DebugGL4 is added to the classpath by Gradle.
Why? DebugGL4 intercepts all GL calls and checks if OpenGL reported an error after the call, and if so, it throws an exception. This can be quite helpful with tracking down invalid GL calls that otherwise go unnoticed.
This wraps the
GL4
instance inDebugGL4
when the plugin is turned on while debug logging is enabled, if it is present on the classpath. When launching HD throughHdPluginTest
,DebugGL4
is added to the classpath by Gradle.Why?
DebugGL4
intercepts all GL calls and checks if OpenGL reported an error after the call, and if so, it throws an exception. This can be quite helpful with tracking down invalid GL calls that otherwise go unnoticed.Depends on #261