Package org.lwjgl.egl

Interface EGLDebugMessageKHRCallbackI

  • All Superinterfaces:
    CallbackI, CallbackI.V, Pointer
    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.

    public interface EGLDebugMessageKHRCallbackI
    extends CallbackI.V
    Instances of this interface may be passed to the DebugMessageControlKHR method.


     void (*) (
         EGLenum error,
         char const *command,
         EGLint messageType,
         EGLLabelKHR threadLabel,
         EGLLabelKHR objectLabel,
         char const *message
    • Field Detail


        static final java.lang.String SIGNATURE
    • Method Detail

      • getSignature

        default java.lang.String getSignature()
        Description copied from interface: CallbackI
        Returns the dyncall signature for this callback function. [INTERNAL API]
        Specified by:
        getSignature in interface CallbackI
        the dyncall signature
      • callback

        default void callback​(long args)
        Description copied from interface: CallbackI.V
        Will be called by native code.
        Specified by:
        callback in interface CallbackI.V
        args - pointer to a DCArgs iterator
      • invoke

        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 threadLabel will be NULL if not set by the application. If the message is from an internal thread, the label will be NULL.
        objectLabel - will contain the label attached to the primary object of the message; Labels will be NULL if 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 objectLabel may be NULL even 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 NULL and should not be assumed otherwise.