- All Known Implementing Classes:
- Functional Interface:
- This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.
@FunctionalInterface public interface EGLDebugMessageKHRCallbackI extends CallbackI.VInstances of this interface may be passed to the
void (*) ( EGLenum error, char const *command, EGLint messageType, EGLLabelKHR threadLabel, EGLLabelKHR objectLabel, char const *message )
Nested Class Summary
Nested classes/interfaces inherited from interface org.lwjgl.system.CallbackI
CallbackI.B, CallbackI.D, CallbackI.F, CallbackI.I, CallbackI.J, CallbackI.P, CallbackI.S, CallbackI.V, CallbackI.Z
All Methods Instance Methods Abstract Methods Default Methods Modifier and Type Method Description
callback(long args)Will be called by native code.
getSignature()Returns the dyncall signature for this callback function.
invoke(int error, long command, int messageType, long threadLabel, long objectLabel, long message)Will be called when a debug message is generated.
default java.lang.String getSignature()Description copied from interface:
CallbackIReturns the dyncall signature for this callback function. [INTERNAL API]
default void callback(long args)Description copied from interface:
CallbackI.VWill be called by native code.
void invoke(int error, long command, int messageType, long threadLabel, long objectLabel, long message)Will be called when a debug message is generated.
error- will contain an EGL error code, or
SUCCESS, as applicable
command- will contain a pointer to a string. Example "eglBindApi".
messageType- will contain one of the debug message types
threadLabel- will contain the label attached to the current thread. The
NULLif not set by the application. If the message is from an internal thread, the label will be
objectLabel- will contain the label attached to the primary object of the message; Labels will be
NULLif not set by the application. The primary object should be the object the function operates on, see table 13.2 which provides the recommended mapping between functions and their primary object. This
NULLeven though the application labeled the object. This is because it is possible an error was raised while executing the command before the primary object was validated, therefore its label can not be included in the callback.
message- will contain a platform specific debug string message; This string should provide added information to the application developer regarding the condition that generated the message. The format of a message is implementation-defined, although it should represent a concise description of the event that caused the message to be generated. Message strings can be
NULLand should not be assumed otherwise.