WindowManager Destroying surface11/14/2023 ![]() ![]() If the running window manager does not support this protocol, the user will not be notified if the application locks up. GLFW uses the EWMH _NET_WM_PING protocol, allowing the window manager notify the user when the application has stopped responding, i.e. If the running window manager does not support this protocol, the close callback will never be called. ![]() GLFW uses the ICCCM WM_DELETE_WINDOW protocol to intercept the user attempting to close the GLFW window. If the running window manager does not support this property, the GLFW_DECORATED hint will have no effect. GLFW uses the _MOTIF_WM_HINTS window property to support borderless windows. In order for applications and window managers to work well together, a number of standards and conventions have been developed that regulate behavior outside the scope of the X11 API most importantly the Inter-Client Communication Conventions Manual (ICCCM) and Extended Window Manager Hints (EWMH) standards. X11 extensions, protocols and IPC standardsĪs GLFW uses Xlib directly, without any intervening toolkit library, it has sole responsibility for interacting well with the many and varied window managers in use on Unix-like systems. Any part of this information may change in future versions of GLFW and that will not be considered a breaking API change. The information in this guide is not a part of GLFW API, but merely preconditions for some parts of the library to function on a given machine. It lists what are essentially implementation details, but which are nonetheless vital knowledge for developers intending to deploy their applications on a wide range of machines. This guide describes the various API extensions used by this version of GLFW. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |