Abstract
Can currently be fetched from the git repository found here: http://repo.or.cz/w/cl-glfw.gitOr via the asdf-install package:
Download ASDF package from http://wvr.me.uk/cl-glfw/cl-glfw_current.tar.gz
The cl-glfw dictionary
[Constant]
+accelerated+
[Constant]
+accum-alpha-bits+
[Constant]
+accum-blue-bits+
[Constant]
+accum-green-bits+
[Constant]
+accum-red-bits+
[Constant]
+active+
[Constant]
+alpha-bits+
[Constant]
+alpha-map-bit+
[Constant]
+auto-poll-events+
[Constant]
+aux-buffers+
[Constant]
+axes+
[Constant]
+blue-bits+
[Constant]
+build-mipmaps-bit+
[Constant]
+buttons+
[Constant]
+depth-bits+
[Constant]
+false+
[Constant]
+fsaa-samples+
[Constant]
+fullscreen+
[Constant]
+green-bits+
[Constant]
+iconified+
[Constant]
+infinity+
[Constant]
+joystick-1+
[Constant]
+joystick-10+
[Constant]
+joystick-11+
[Constant]
+joystick-12+
[Constant]
+joystick-13+
[Constant]
+joystick-14+
[Constant]
+joystick-15+
[Constant]
+joystick-16+
[Constant]
+joystick-2+
[Constant]
+joystick-3+
[Constant]
+joystick-4+
[Constant]
+joystick-5+
[Constant]
+joystick-6+
[Constant]
+joystick-7+
[Constant]
+joystick-8+
[Constant]
+joystick-9+
[Constant]
+joystick-last+
[Constant]
+key-backspace+
[Constant]
+key-del+
[Constant]
+key-down+
[Constant]
+key-end+
[Constant]
+key-enter+
[Constant]
+key-esc+
[Constant]
+key-f1+
[Constant]
+key-f10+
[Constant]
+key-f11+
[Constant]
+key-f12+
[Constant]
+key-f13+
[Constant]
+key-f14+
[Constant]
+key-f15+
[Constant]
+key-f16+
[Constant]
+key-f17+
[Constant]
+key-f18+
[Constant]
+key-f19+
[Constant]
+key-f2+
[Constant]
+key-f20+
[Constant]
+key-f21+
[Constant]
+key-f22+
[Constant]
+key-f23+
[Constant]
+key-f24+
[Constant]
+key-f25+
[Constant]
+key-f3+
[Constant]
+key-f4+
[Constant]
+key-f5+
[Constant]
+key-f6+
[Constant]
+key-f7+
[Constant]
+key-f8+
[Constant]
+key-f9+
[Constant]
+key-home+
[Constant]
+key-insert+
[Constant]
+key-kp-0+
[Constant]
+key-kp-1+
[Constant]
+key-kp-2+
[Constant]
+key-kp-3+
[Constant]
+key-kp-4+
[Constant]
+key-kp-5+
[Constant]
+key-kp-6+
[Constant]
+key-kp-7+
[Constant]
+key-kp-8+
[Constant]
+key-kp-9+
[Constant]
+key-kp-add+
[Constant]
+key-kp-decimal+
[Constant]
+key-kp-divide+
[Constant]
+key-kp-enter+
[Constant]
+key-kp-equal+
[Constant]
+key-kp-multiply+
[Constant]
+key-kp-subtract+
[Constant]
+key-lalt+
[Constant]
+key-last+
[Constant]
+key-lctrl+
[Constant]
+key-left+
[Constant]
+key-lshift+
[Constant]
+key-pagedown+
[Constant]
+key-pageup+
[Constant]
+key-ralt+
[Constant]
+key-rctrl+
[Constant]
+key-repeat+
[Constant]
+key-right+
[Constant]
+key-rshift+
[Constant]
+key-space+
[Constant]
+key-special+
[Constant]
+key-tab+
[Constant]
+key-unknown+
[Constant]
+key-up+
[Constant]
+mouse-button-1+
[Constant]
+mouse-button-2+
[Constant]
+mouse-button-3+
[Constant]
+mouse-button-4+
[Constant]
+mouse-button-5+
[Constant]
+mouse-button-6+
[Constant]
+mouse-button-7+
[Constant]
+mouse-button-8+
[Constant]
+mouse-button-last+
[Constant]
+mouse-button-left+
[Constant]
+mouse-button-middle+
[Constant]
+mouse-button-right+
[Constant]
+mouse-cursor+
[Constant]
+no-rescale-bit+
[Constant]
+nowait+
[Constant]
+opened+
[Constant]
+origin-ul-bit+
[Constant]
+present+
[Constant]
+press+
[Constant]
+red-bits+
[Constant]
+refresh-rate+
[Constant]
+release+
[Constant]
+stencil-bits+
[Constant]
+stereo+
[Constant]
+sticky-keys+
[Constant]
+sticky-mouse-buttons+
[Constant]
+system-keys+
[Constant]
+true+
[Constant]
+wait+
[Constant]
+window+
[Constant]
+window-no-resize+
[Function]
broadcast-cond cond => resultParameters cond A condition variable object handle. Description The function restarts all the threads that are waiting on the condition variable cond. If no threads are waiting on cond, nothing happens. Notes When several threads are waiting for the condition variable, the order in which threads are started depends on operating system scheduling rules, and may vary from system to system and from time to time.
[Function]
close-window => resultThe function closes an opened window and destroys the associated OpenGL™ context.
[Function]
create-cond => resultReturn values The function returns a condition variable handle, or NULL if the condition variable could not be created. Description The function creates a condition variable object, which can be used to synchronize threads.
[Function]
create-mutex => resultReturn values The function returns a mutex handle, or NULL if the mutex could not be created. Description The function creates a mutex object, which can be used to control access to data that is shared between threads.
[Function]
create-thread fun arg => resultParameters fun A pointer to a function that acts as the entry point for the new thread. The function should have the following C language prototype: void GLFWCALL functionname( void *arg ); Where functionname is the name of the thread function, and arg is the user supplied argument (see below). arg An arbitrary argument for the thread. arg will be passed as the argument to the thread function pointed to by fun. For instance, arg can point to data that is to be processed by the thread. Return values The function returns a thread identification number if the thread was created successfully. This number is always positive. If the function fails, a negative number is returned. Description The function creates a new thread, which executes within the same address space as the calling process. The thread entry point is specified with the fun argument. Once the thread function fun returns, the thread dies. Notes Even if the function returns a positive thread ID, indicating that the thread was created successfully, the thread may be unable to execute, for instance if the thread start address is not a valid thread entry point.
[Macro]
defcfun+doc (c-name lisp-name) return-type (declaration* statement*) docstring => result
[Macro]
defcfun+out+doc (c-name lisp-name) return-type (declaration* statement*) docstring => result
[Function]
destroy-cond cond => resultParameters cond A condition variable object handle. Description The function destroys a condition variable object. After a condition variable object has been destroyed, it may no longer be used by any thread.
[Function]
destroy-mutex mutex => resultParameters mutex A mutex object handle. Description The function destroys a mutex object. After a mutex object has been destroyed, it may no longer be used by any thread.
[Function]
destroy-thread id => resultParameters ID A thread identification handle, which is returned by glfw::CreateThread or glfw::GetThreadID. Description The function kills a running thread and removes it from the thread list. Notes This function is a very dangerous operation, which may interrupt a thread in the middle of an important operation, and its use is discouraged. You should always try to end a thread in a graceful way using thread communication, and use glfw::WaitThread in order to wait for the thread to die.
[Function]
disable token => resultParameters token A value specifying a feature to enable or disable. Valid tokens are listed in table 3.8. Return values none Description glfw::Enable is used to enable a certain feature, while glfw::Disable is used to disable it. Below follows a description of each feature. +AUTO_POLL_EVENTS+ When +AUTO_POLL_EVENTS+ is enabled, glfw::PollEvents is automatically called each time that glfw::SwapBuffers is called. When +AUTO_POLL_EVENTS+ is disabled, calling glfw::SwapBuffers will not result in a call to glfw::PollEvents. This can be useful if glfw::SwapBuffers needs to be called from within a callback function, since calling glfw::PollEvents from a callback function is not allowed. +KEY_REPEAT+ When +KEY_REPEAT+ is enabled, the key and character callback functions are called repeatedly when a key is held down long enough (according to the system key repeat configuration). When +KEY_REPEAT+ is disabled, the key and character callback functions are only called once when a key is pressed (and once when it is released). +MOUSE_CURSOR+ When +MOUSE_CURSOR+ is enabled, the mouse cursor is visible, and mouse coordinates are relative to the upper left corner of the client area of the GLFW window. The coordinates are limited to the client area of the window. When +MOUSE_CURSOR+ is disabled, the mouse cursor is invisible, and mouse coordinates are not limited to the drawing area of the window. It is as if the mouse coordinates are recieved directly from the mouse, without being restricted or manipulated by the windowing system. +STICKY_KEYS+ When +STICKY_KEYS+ is enabled, keys which are pressed will not be released until they are physically released and checked with glfw::GetKey. This behavior makes it possible to catch keys that were pressed and then released again between two calls to glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers, which would otherwise have been reported as released. Care should be taken when using this mode, since keys that are not checked with glfw::GetKey will never be released. Note also that enabling +STICKY_KEYS+ does not affect the behavior of the keyboard callback functionality. When +STICKY_KEYS+ is disabled, the status of a key that is reported by glfwGetKey is always the physical state of the key. Disabling +STICKY_KEYS+ also clears the sticky information for all keys. +STICKY_MOUSE_BUTTONS+ When +STICKY_MOUSE_BUTTONS+ is enabled, mouse buttons that are pressed will not be released until they are physically released and checked with glfw::GetMouseButton. This behavior makes it possible to catch mouse buttons which were pressed and then released again between two calls to glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers, which would otherwise have been reported as released. Care should be taken when using this mode, since mouse buttons that are not checked with glfw::GetMouseButton will never be released. Note also that enabling +STICKY_MOUSE_BUTTONS+ does not affect the behavior of the mouse button callback functionality. When +STICKY_MOUSE_BUTTONS+ is disabled, the status of a mouse button that is reported by glfwGetMouseButton is always the physical state of the mouse button. Disabling +STICKY_MOUSE_BUTTONS+ also clears the sticky information for all mouse buttons. +SYSTEM_KEYS+ When +SYSTEM_KEYS+ is enabled, pressing standard system key combinations, such as ALT+TAB under Windows, will give the normal behavior. Note that when ALT+TAB is issued under Windows in this mode so that the GLFW application is deselected when GLFW is operating in fullscreen mode, the GLFW application window will be minimized and the video mode will be set to the original desktop mode. When the GLFW application is re-selected, the video mode will be set to the GLFW video mode again. When +SYSTEM_KEYS+ is disabled, pressing standard system key combinations will have no effect, since those key combinations are blocked by GLFW. This mode can be useful in situations when the GLFW program must not be interrupted (normally for games in fullscreen mode).High-level convenience macro for initializing glfw, opening a window (given the optional window parameters), setting the title given, running setup-forms and then running forms in a loop, with calls to swap-buffers after each loop iteration. The loop is in a block named do-window [so can be exited by a call to (return-from glfw:do-window)]. If the window is closed, the loop is also exited.
[Function]
enable token => resultParameters token A value specifying a feature to enable or disable. Valid tokens are listed in table 3.8. Return values none Description glfw::Enable is used to enable a certain feature, while glfw::Disable is used to disable it. Below follows a description of each feature. +AUTO_POLL_EVENTS+ When +AUTO_POLL_EVENTS+ is enabled, glfw::PollEvents is automatically called each time that glfw::SwapBuffers is called. When +AUTO_POLL_EVENTS+ is disabled, calling glfw::SwapBuffers will not result in a call to glfw::PollEvents. This can be useful if glfw::SwapBuffers needs to be called from within a callback function, since calling glfw::PollEvents from a callback function is not allowed. +KEY_REPEAT+ When +KEY_REPEAT+ is enabled, the key and character callback functions are called repeatedly when a key is held down long enough (according to the system key repeat configuration). When +KEY_REPEAT+ is disabled, the key and character callback functions are only called once when a key is pressed (and once when it is released). +MOUSE_CURSOR+ When +MOUSE_CURSOR+ is enabled, the mouse cursor is visible, and mouse coordinates are relative to the upper left corner of the client area of the GLFW window. The coordinates are limited to the client area of the window. When +MOUSE_CURSOR+ is disabled, the mouse cursor is invisible, and mouse coordinates are not limited to the drawing area of the window. It is as if the mouse coordinates are recieved directly from the mouse, without being restricted or manipulated by the windowing system. +STICKY_KEYS+ When +STICKY_KEYS+ is enabled, keys which are pressed will not be released until they are physically released and checked with glfw::GetKey. This behavior makes it possible to catch keys that were pressed and then released again between two calls to glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers, which would otherwise have been reported as released. Care should be taken when using this mode, since keys that are not checked with glfw::GetKey will never be released. Note also that enabling +STICKY_KEYS+ does not affect the behavior of the keyboard callback functionality. When +STICKY_KEYS+ is disabled, the status of a key that is reported by glfw::GetKey is always the physical state of the key. Disabling +STICKY_KEYS+ also clears the sticky information for all keys. +STICKY_MOUSE_BUTTONS+ When +STICKY_MOUSE_BUTTONS+ is enabled, mouse buttons that are pressed will not be released until they are physically released and checked with glfw::GetMouseButton. This behavior makes it possible to catch mouse buttons which were pressed and then released again between two calls to glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers, which would otherwise have been reported as released. Care should be taken when using this mode, since mouse buttons that are not checked with glfw::GetMouseButton will never be released. Note also that enabling +STICKY_MOUSE_BUTTONS+ does not affect the behavior of the mouse button callback functionality. When +STICKY_MOUSE_BUTTONS+ is disabled, the status of a mouse button that is reported by glfw::GetMouseButton is always the physical state of the mouse button. Disabling +STICKY_MOUSE_BUTTONS+ also clears the sticky information for all mouse buttons. +SYSTEM_KEYS+ When +SYSTEM_KEYS+ is enabled, pressing standard system key combinations, such as ALT+TAB under Windows, will give the normal behavior. Note that when ALT+TAB is issued under Windows in this mode so that the GLFW application is deselected when GLFW is operating in fullscreen mode, the GLFW application window will be minimized and the video mode will be set to the original desktop mode. When the GLFW application is re-selected, the video mode will be set to the GLFW video mode again. When +SYSTEM_KEYS+ is disabled, pressing standard system key combinations will have no effect, since those key combinations are blocked by GLFW. This mode can be useful in situations when the GLFW program must not be interrupted (normally for games in fullscreen mode).
[Function]
extension-supported extension => resultParameters extension A null terminated ISO 8859-1 string containing the name of an OpenGL™ extension. Return values The function returns t if the extension is supported. Otherwise it returns nil. Description The function does a string search in the list of supported OpenGL™ extensions to find if the specified extension is listed. Notes An OpenGL™ context must be created before this function can be called (i.e. an OpenGL™ window must have been opened with glfw::OpenWindow). In addition to checking for OpenGL™ extensions, GLFW also checks for extensions in the operating system “glue API”, such as WGL extensions under Windows and glX extensions under the X Window System.
[Function]
free-image img => resultParameters img Pointer to a GLFWimage struct. Description The function frees any memory occupied by a loaded image, and clears all the fields of the GLFWimage struct. Any image that has been loaded by the glfw::ReadImage function should be deallocated using this function, once the image is not needed anymore.
[Function]
get-desktop-mode => resultParameters mode Pointer to a GLFWvidmode structure, which will be filled out by the function. Return values The GLFWvidmode structure pointed to by mode is filled out with the desktop video mode. Description The function returns the desktop video mode in a GLFWvidmode structure. See glfwGetVideoModes for a definition of the GLFWvidmode structure. Notes The color depth of the desktop display is always reported as the number of bits for each individual color component (red, green and blue), even if the desktop is not using an RGB or RGBA color format. For instance, an indexed 256 color display may report RedBits = 3, GreenBits = 3 and BlueBits = 2, which adds up to 8 bits in total. The desktop video mode is the video mode used by the desktop, not the current video mode (which may differ from the desktop video mode if the GLFW window is a fullscreen window).
[Function]
get-gl-version => resultReturn values The function returns the major and minor version numbers and the revision for the currently used OpenGL™ implementation as a list (major minor rev). Description The function returns the OpenGL™ implementation version. This is a convenient function that parses the version number information from the string returned by calling glGetString( GL_VERSION ). The OpenGL™ version information can be used to determine what functionality is supported by the used OpenGL™ implementation. Notes An OpenGL™ context must be created before this function can be called (i.e. an OpenGL™ window must have been opened with glfwOpenWindow).
[Function]
get-joystick-buttons joy numbuttons => resultParameters joy A joystick identifier, which should be +JOYSTICK_n+ where n is in the range 1 to 16. numbuttons Specifies how many buttons should be returned. Return values A list that will hold the button states for all requested buttons. The function returns the number of actually returned buttons. This is the minimum of numbuttons and the number of buttons supported by the joystick. If the joystick is not supported or connected, the function will return 0 (zero). Description The function queries the current state of one or more buttons of a joystick. The button states are returned in an array, where the first element represents the first button of the joystick. Each state can be either +PRESS+ or +RELEASE+ If numbuttons exceeds the number of buttons supported by the joystick, or if the joystick is not available, the unused elements in the buttons array will be set to +RELEASE+ Notes The joystick state is updated every time the function is called, so there is no need to call glfw::PollEvents or glfw::WaitEvents for joystick state to be updated. Use glfw::GetJoystickParam to retrieve joystick capabilities, such as joystick availability and number of supported buttons. No window has to be opened for joystick input to be valid.
[Function]
get-joystick-param joy param => resultParameters joy A joystick identifier, which should be +JOYSTICK_n+ where n is in the range 1 to 16. param A token selecting which parameter the function should return (see table 3.5). Return values The function returns different parameters depending on the value of param. Table 3.5 lists valid param values, and their corresponding return values. Description The function is used for acquiring various properties of a joystick. Notes The joystick information is updated every time the function is called. No window has to be opened for joystick information to be valid.
[Function]
get-joystick-pos joy numaxes => resultParameters joy A joystick identifier, which should be +JOYSTICK_n+ where n is in the range 1 to 16. numaxes Specifies how many axes should be returned. Return values An list that will hold the positional values for all requested axes. If the joystick is not supported or connected, the function will return nil. Description The function queries the current position of one or more axes of a joystick. The positional values are returned in an array, where the first element represents the first axis of the joystick (normally the X axis). Each position is in the range -1.0 to 1.0. Where applicable, the positive direction of an axis is right, forward or up, and the negative direction is left, back or down. If numaxes exceeds the number of axes supported by the joystick, or if the joystick is not available, the unused elements in the pos array will be set to 0.0 (zero). Notes The joystick state is updated every time the function is called, so there is no need to call glfw::PollEvents or glfw::WaitEvents for joystick state to be updated. Use glfw::GetJoystickParam to retrieve joystick capabilities, such as joystick availability and number of supported axes. No window has to be opened for joystick input to be valid.
[Function]
get-key key => resultParameters key A keyboard key identifier, which can be either an uppercase printable ISO 8859-1 (Latin 1) character (e.g. 'A', '3' or '.'), or a special key identifier. Table 3.3 lists valid special key identifiers. Return values The function returns +PRESS+ if the key is held down, or +RELEASE+ if the key is not held down. Description The function queries the current state of a specific keyboard key. The physical location of each key depends on the system keyboard layout setting. Notes The constant +KEY_SPACE+ is equal to 32, which is the ISO 8859-1 code for space. Not all key codes are supported on all systems. Also, while some keys are available on some keyboard layouts, they may not be available on other keyboard layouts. For systems that do not distinguish between left and right versions of modifier keys (shift, alt and control), the left version is used (e.g. +KEY_LSHIFT+) A window must be opened for the function to have any effect, and glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers must be called before any keyboard events are recorded and reported by glfw::GetKey.
[Function]
get-mouse-button button => resultParameters button A mouse button identifier, which can be one of the mouse button identifiers listed in table 3.4. Return values The function returns +PRESS+ if the mouse button is held down, or +RELEASE+ if the mouse button is not held down. Description The function queries the current state of a specific mouse button. Notes A window must be opened for the function to have any effect, and glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers must be called before any mouse button events are recorded and reported by glfw::GetMouseButton. +MOUSE_BUTTON_LEFT+ is equal to +MOUSE_BUTTON_1+ +MOUSE_BUTTON_RIGHT+ is equal to +MOUSE_BUTTON_2+ +MOUSE_BUTTON_MIDDLE+ is equal to +MOUSE_BUTTON_3+
[Function]
get-mouse-pos => resultReturn values The function returns the current mouse position in xpos and ypos. Description The function returns the current mouse position. If the cursor is not hidden, the mouse position is the cursor position, relative to the upper left corner of the window and limited to the client area of the window. If the cursor is hidden, the mouse position is a virtual absolute position, not limited to any boundaries except to those implied by the maximum number that can be represented by a signed integer (normally -2147483648 to +2147483647). Notes A window must be opened for the function to have any effect, and glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers must be called before any mouse movements are recorded and reported by glfw::GetMousePos.
[Function]
get-mouse-wheel => resultReturn values The function returns the current mouse wheel position. Description The function returns the current mouse wheel position. The mouse wheel can be thought of as a third mouse axis, which is available as a separate wheel or up/down stick on some mice. Notes A window must be opened for the function to have any effect, and glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers must be called before any mouse wheel movements are recorded and reported by glfw::GetMouseWheel.
[Function]
get-number-of-processors => resultReturn values The function returns the number of active processors in the system. Description The function determines the number of active processors in the system. Notes Systems with several logical processors per physical processor, also known as SMT (Symmetric Multi Threading) processors, will report the number of logical processors.
[Function]
get-proc-address procname => resultParameters procname A null terminated ISO 8859-1 string containing the name of an OpenGL™ extension function. Return values The function returns the pointer to the specified OpenGL™ function if it is supported, otherwise NULL is returned. Description The function acquires the pointer to an OpenGL™ extension function. Some (but not all) OpenGL™ extensions define new API functions, which are usually not available through normal linking. It is therefore necessary to get access to those API functions at runtime. Notes An OpenGL™ context must be created before this function can be called (i.e. an OpenGL™ window must have been opened with glfw::OpenWindow). Some systems do not support dynamic function pointer retrieval, in which case glfw::GetProcAddress will always return NULL.
[Function]
get-thread-id => resultReturn values The function returns a thread identification handle for the calling thread. Description The function determines the thread ID for the calling thread. The ID is the same value as was returned by glfw::CreateThread when the thread was created.
[Function]
get-time => resultReturn values The function returns the value of the high precision timer. The time is measured in seconds, and is returned as a double precision floating point value. Description The function returns the state of a high precision timer. Unless the timer has been set by the glfw::SetTime function, the time is measured as the number of seconds that have passed since glfw::Init was called. Notes The resolution of the timer depends on which system the program is running on. The worst case resolution is somewhere in the order of 10 ms, while for most systems the resolution should be better than 1 μs.
[Function]
get-version => resultReturn values The function returns the major and minor version numbers and the revision for the currently linked GLFW library as a list (major minor rev).
[Function]
get-video-modes maxcount => resultParameters maxcount Maximum number of video modes that list vector can hold. Return values The function returns the number of detected video modes (this number will never exceed maxcount). The list vector is filled out with the video modes that are supported by the system. Description The function returns a list of supported video modes. Each video mode is represented by a list of the form: (width height redbits greenbits bluebits) Notes The returned list is sorted, first by color depth (RedBits + GreenBits + BlueBits), and then by resolution (Width × Height), with the lowest resolution, fewest bits per pixel mode first.
[Function]
get-window-param param => resultParameters param A token selecting which parameter the function should return (see table 3.2). Return values The function returns different parameters depending on the value of param. Table 3.2 lists valid param values, and their corresponding return values. Description The function is used for acquiring various properties of an opened window. Notes +ACCELERATED+ is only supported under Windows. Other systems will always return GL::+TRUE+. Under Windows, +ACCELERATED+ means that the OpenGL™ renderer is a 3rd party renderer, rather than the fallback Microsoft software OpenGL™ renderer. In other words, it is not a real guarantee that the OpenGL™ renderer is actually hardware accelerated.
[Function]
get-window-size => resultThe function is used for determining the size of an opened window. The returned values are dimensions of the client area of the window (i.e. excluding any window borders and decorations). (list width height)
[Function]
iconify-window => resultIconify a window. If the window is in fullscreen mode, then the desktop video mode will be restored.
[Function]
init => resultReturn values If the function succeeds, t is returned. If the function fails, nil is returned. The glfwInit function initializes GLFW. No other GLFW functions may be used before this function has been called. Notes This function may take several seconds to complete on some systems, while on other systems it may take only a fraction of a second to complete.
[Function]
load-memory-texture-2d data size flags => resultParameters data The memory buffer holding the contents of the file that should be loaded. size The size, in bytes, of the memory buffer. flags Flags for controlling the texture loading process. Valid flags are listed in table 3.7. Return values The function returns t if the texture was loaded successfully. Otherwise nil is returned. Description The function reads an image from the memory buffer specified by the parameter data and uploads the image to OpenGL™ texture memory (using the glTexImage2D function). If the +BUILD_MIPMAPS_BIT+ flag is set, all mipmap levels for the loaded texture are generated and uploaded to texture memory. Unless the flag +ORIGIN_UL_BIT+ is set, the origin of the texture is the lower left corner of the loaded image. If the flag +ORIGIN_UL_BIT+ is set, however, the first pixel is the upper left corner. For single component images (i.e. gray scale), the texture is uploaded as an alpha mask if the flag +ALPHA_MAP_BIT+ flag is set, otherwise it is uploaded as a luminance texture. Notes glfw::LoadMemoryTexture2D supports the Truevision Targa version 1 file format (.TGA). Supported pixel formats are: 8-bit gray scale, 8-bit paletted (24/32-bit color), 24-bit true color and 32-bit true color + alpha. Paletted images are translated into true color or true color + alpha pixel formats. The read texture is always rescaled to the nearest larger 2m × 2n resolution using bilinear interpolation, if necessary, since OpenGL™ requires textures to have a 2m × 2n resolution. If the GL_SGIS_generate_mipmap extension, which is usually hardware accelerated, is supported by the OpenGL™ implementation it will be used for mipmap generation. Otherwise the mipmaps will be generated by GLFW in software. Since OpenGL™ 1.0 does not support single component alpha maps, alpha map textures are converted to RGBA format under OpenGL™ 1.0 when the +ALPHA_MAP_BIT+ flag is set and the loaded texture is a single component texture. The red, green and blue components are set to 1.0.
[Function]
load-texture-2d name flags => resultParameters name An ISO 8859-1 string holding the name of the file that should be loaded. flags Flags for controlling the texture loading process. Valid flags are listed in table 3.7. Return values The function returns t if the texture was loaded successfully. Otherwise nil is returned. Description The function reads an image from the file specified by the parameter name and uploads the image to OpenGL™ texture memory (using the glTexImage2D function). If the +BUILD_MIPMAPS_BIT+ flag is set, all mipmap levels for the loaded texture are generated and uploaded to texture memory. Unless the flag +ORIGIN_UL_BIT+ is set, the origin of the texture is the lower left corner of the loaded image. If the flag +ORIGIN_UL_BIT+ is set, however, the first pixel is the upper left corner. For single component images (i.e. gray scale), the texture is uploaded as an alpha mask if the flag +ALPHA_MAP_BIT+ flag is set, otherwise it is uploaded as a luminance texture. Notes glfw::LoadTexture2D supports the Truevision Targa version 1 file format (.TGA). Supported pixel formats are: 8-bit gray scale, 8-bit paletted (24/32-bit color), 24-bit true color and 32-bit true color + alpha. Paletted images are translated into true color or true color + alpha pixel formats. The read texture is always rescaled to the nearest larger 2m × 2n resolution using bilinear interpolation, if necessary, since OpenGL™ requires textures to have a 2m × 2n resolution. If the GL_SGIS_generate_mipmap extension, which is usually hardware accelerated, is supported by the OpenGL™ implementation it will be used for mipmap generation. Otherwise the mipmaps will be generated by GLFW in software. Since OpenGL™ 1.0 does not support single component alpha maps, alpha map textures are converted to RGBA format under OpenGL™ 1.0 when the +ALPHA_MAP_BIT+ flag is set and the loaded texture is a single component texture. The red, green and blue components are set to 1.0.
[Function]
load-texture-image-2d img flags => resultParameters img Pointer to a GLFWimage struct holding the information about the image to be loaded. flags Flags for controlling the texture loading process. Valid flags are listed in table 3.7. Return values The function returns t if the texture was loaded successfully. Otherwise nil is returned. Description The function uploads the image specified by the parameter img to OpenGL™ texture memory (using the glTexImage2D function). If the +BUILD_MIPMAPS_BIT+ flag is set, all mipmap levels for the loaded texture are generated and uploaded to texture memory. Unless the flag +ORIGIN_UL_BIT+ is set, the origin of the texture is the lower left corner of the loaded image. If the flag +ORIGIN_UL_BIT+ is set, however, the first pixel is the upper left corner. For single component images (i.e. gray scale), the texture is uploaded as an alpha mask if the flag +ALPHA_MAP_BIT+ flag is set, otherwise it is uploaded as a luminance texture. Notes glfw::LoadTextureImage2D supports the Truevision Targa version 1 file format (.TGA). Supported pixel formats are: 8-bit gray scale, 8-bit paletted (24/32-bit color), 24-bit true color and 32-bit true color + alpha. Paletted images are translated into true color or true color + alpha pixel formats. The read texture is always rescaled to the nearest larger 2m × 2n resolution using bilinear interpolation, if necessary, since OpenGL™ requires textures to have a 2m × 2n resolution. If the GL_SGIS_generate_mipmap extension, which is usually hardware accelerated, is supported by the OpenGL™ implementation it will be used for mipmap generation. Otherwise the mipmaps will be generated by GLFW in software. Since OpenGL™ 1.0 does not support single component alpha maps, alpha map textures are converted to RGBA format under OpenGL™ 1.0 when the +ALPHA_MAP_BIT+ flag is set and the loaded texture is a single component texture. The red, green and blue components are set to 1.0.
[Function]
lock-mutex mutex => resultParameters mutex A mutex object handle. Description The function will acquire a lock on the selected mutex object. If the mutex is already locked by another thread, the function will block the calling thread until it is released by the locking thread. Once the function returns, the calling thread has an exclusive lock on the mutex. To release the mutex, call glfw::UnlockMutex.width The width of the window. If width is zero, it will be calculated as width = 4/3 height, if height is not zero. If both width and height are zero, then width will be set to 640. height The height of the window. If height is zero, it will be calculated as height = 3/4 width, if width is not zero. If both width and height are zero, then height will be set to 480. redbits, greenbits, bluebits The number of bits to use for each color component of the color buffer (0 means default color depth). For instance, setting redbits=5, greenbits=6, and bluebits=5 will generate a 16-bit color buffer, if possible. alphabits The number of bits to use for the alpha buffer (0 means no alpha buffer). depthbits The number of bits to use for the depth buffer (0 means no depth buffer). stencilbits The number of bits to use for the stencil buffer (0 means no stencil buffer). mode Selects which type of OpenGL™ window to use. mode can be either +WINDOW+, which will generate a normal desktop window, or +FULLSCREEN+ which will generate a window which covers the entire screen. When +FULLSCREEN+ is selected, the video mode will be changed to the resolution that closest matches the width and height parameters. Return values If the function succeeds, t is returned. If the function fails, nil is returned. Description The function opens a window that best matches the parameters given to the function. How well the resulting window matches the desired window depends mostly on the available hardware and OpenGL™ drivers. In general, selecting a fullscreen mode has better chances of generating a close match than does a normal desktop window, since GLFW can freely select from all the available video modes. A desktop window is normally restricted to the video mode of the desktop. Notes For additional control of window properties, see glfw::OpenWindowHint. In fullscreen mode the mouse cursor is hidden by default, and any system screensavers are prohibited from starting. In windowed mode the mouse cursor is visible, and screensavers are allowed to start. To change the visibility of the mouse cursor, use glfwEnable or glfwDisable with the argument +MOUSE_CURSOR+ In order to determine the actual properties of an opened window, use glfw::GetWindowParam and glfw::GetWindowSize (or glfw::SetWindowSizeCallback).
[Function]
open-window-hint target hint => resulttarget Can be any of the constants in the table 3.1. hint An integer giving the value of the corresponding target (see table 3.1). Description The function sets additional properties for a window that is to be opened. For a hint to be registered, the function must be called before calling glfw::OpenWindow. When the glfw::OpenWindow function is called, any hints that were registered with the glfw::OpenWindowHint function are used for setting the corresponding window properties, and then all hints are reset to their default values. Notes In order to determine the actual properties of an opened window, use glfw::GetWindowParam (after the window has been opened). +STEREO+ is a hard constraint. If stereo rendering is requested, but no stereo rendering capable pixel formats / visuals are available, glfw::OpenWindow will fail. The +REFRESH_RATE+ property should be used with caution. Most systems have default values for monitor refresh rates that are optimal for the specific system. Specifying the refresh rate can override these settings, which can result in suboptimal operation. The monitor may be unable to display the resulting video signal, or in the worst case it may even be damaged!
[Function]
poll-events => resultDescription The function is used for polling for events, such as user input and window resize events. Upon calling this function, all window states, keyboard states and mouse states are updated. If any related callback functions are registered, these are called during the call to glfwPollEvents. Notes glfwPollEvents is called implicitly from glfwSwapBuffers if +AUTO_POLL_EVENTS+ is enabled (default). Thus, if glfwSwapBuffers is called frequently, which is normally the case, there is no need to call glfwPollEvents.
[Function]
read-image name img flags => resultParameters name A null terminated ISO 8859-1 string holding the name of the file that should be read. img Pointer to a GLFWimage struct, which will hold the information about the loaded image (if the read was successful). flags Flags for controlling the image reading process. Valid flags are listed in table 3.6 Return values The function returns t if the image was loaded successfully. Otherwise nil is returned. Description The function reads an image from the file specified by the parameter name and returns the image information and data in a GLFWimage structure, which has the following definition: § ¤ typedef struct { int Width, Height; // Image dimensions int Format; // OpenGL pixel format int BytesPerPixel; // Number of bytes per pixel unsigned char *Data; // Pointer to pixel data } GLFWimage; ¦ ¥ Width and Height give the dimensions of the image. Format specifies an OpenGL™ pixel format, which can be GL_LUMINANCE or GL_ALPHA (for gray scale images), GL_RGB or GL_RGBA. BytesPerPixel specifies the number of bytes per pixel. Data is a pointer to the actual pixel data. By default the read image is rescaled to the nearest larger 2m × 2n resolution using bilinear interpolation, if necessary, which is useful if the image is to be used as an OpenGL™ texture. This behavior can be disabled by setting the +NO_RESCALE_BIT+ flag. Unless the flag +ORIGIN_UL_BIT+ is set, the first pixel in img->Data is the lower left corner of the image. If the flag +ORIGIN_UL_BIT+ is set, however, the first pixel is the upper left corner. For single component images (i.e. gray scale), Format is set to GL_ALPHA if the flag +ALPHA_MAP_BIT+ flag is set, otherwise Format is set to GL_LUMINANCE. Notes glfw::ReadImage supports the Truevision Targa version 1 file format (.TGA). Supported pixel formats are: 8-bit gray scale, 8-bit paletted (24/32-bit color), 24-bit true color and 32-bit true color + alpha. Paletted images are translated into true color or true color + alpha pixel formats. Please note that OpenGL™ 1.0 does not support single component alpha maps, so do not use images with Format = GL_ALPHA directly as textures under OpenGL™ 1.0.
[Function]
read-memory-image data size img flags => resultParameters data The memory buffer holding the contents of the file that should be read. size The size, in bytes, of the memory buffer. img Pointer to a GLFWimage struct, which will hold the information about the loaded image (if the read was successful). flags Flags for controlling the image reading process. Valid flags are listed in table 3.6 Return values The function returns t if the image was loaded successfully. Otherwise nil is returned. Description The function reads an image from the memory buffer specified by the parameter data and returns the image information and data in a GLFWimage structure, which has the following definition: § ¤ typedef struct { int Width, Height; // Image dimensions int Format; // OpenGL pixel format int BytesPerPixel; // Number of bytes per pixel unsigned char *Data; // Pointer to pixel data } GLFWimage; ¦ ¥ Width and Height give the dimensions of the image. Format specifies an OpenGL™ pixel format, which can be GL_LUMINANCE or GL_ALPHA (for gray scale images), GL_RGB or GL_RGBA. BytesPerPixel specifies the number of bytes per pixel. Data is a pointer to the actual pixel data. By default the read image is rescaled to the nearest larger 2m × 2n resolution using bilinear interpolation, if necessary, which is useful if the image is to be used as an OpenGL™ texture. This behavior can be disabled by setting the +NO_RESCALE_BIT+ flag. Unless the flag +ORIGIN_UL_BIT+ is set, the first pixel in img->Data is the lower left corner of the image. If the flag +ORIGIN_UL_BIT+ is set, however, the first pixel is the upper left corner. For single component images (i.e. gray scale), Format is set to GL_ALPHA if the flag +ALPHA_MAP_BIT+ flag is set, otherwise Format is set to GL_LUMINANCE. Notes glfw::ReadMemoryImage supports the Truevision Targa version 1 file format (.TGA). Supported pixel formats are: 8-bit gray scale, 8-bit paletted (24/32-bit color), 24-bit true color and 32-bit true color + alpha. Paletted images are translated into true color or true color + alpha pixel formats. Please note that OpenGL™ 1.0 does not support single component alpha maps, so do not use images with Format = GL_ALPHA directly as textures under OpenGL™ 1.0.
[Function]
restore-window => resultRestore an iconified window. If the window that is restored is in fullscreen mode, then the fullscreen video mode will be restored.
[Function]
set-char-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called every time a printable character is generated by the keyboard. The function should have the following C language prototype: void GLFWCALL functionname( int character, int action ); Where functionname is the name of the callback function, character is a Unicode (ISO 10646) character, and action is either +PRESS+ or +RELEASE+ If cbfun is NULL, any previously selected callback function will be deselected. Return values none Description The function selects which function to be called upon a keyboard character event. The callback function is called every time a key that results in a printable Unicode character is pressed or released. Characters are affected by modifiers (such as shift or alt). A window has to be opened for this function to have any effect. Notes Character events are recorded continuously, but only reported when glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers is called. Control characters, such as tab and carriage return, are not reported to the character callback function, since they are not part of the Unicode character set. Use the key callback function for such events (see glfw::SetKeyCallback). The Unicode character set supports character codes above 255, so never cast a Unicode character to an eight bit data type (e.g. the C language ’char’ type) without first checking that the character code is less than 256. Also note that Unicode character codes 0 to 255 are equal to ISO 8859-1 (Latin 1).
[Function]
set-key-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called every time a key is pressed or released. The function should have the following C language prototype: void GLFWCALL functionname( int key, int action ); Where functionname is the name of the callback function, key is a key identifier, which is an uppercase printable ISO 8859-1 character or a special key identifier (see table 3.3), and action is either +PRESS+ or +RELEASE+ If cbfun is NULL, any previously selected callback function will be deselected. Return values none Description The function selects which function to be called upon a keyboard key event. The callback function is called every time the state of a single key is changed (from released to pressed or vice versa). The reported keys are unaffected by any modifiers (such as shift or alt). A window has to be opened for this function to have any effect. Notes Keyboard events are recorded continuously, but only reported when glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers is called.
[Function]
set-mouse-button-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called every time a mouse button is pressed or released. The function should have the following C language prototype: void GLFWCALL functionname( int button, int action ); Where functionname is the name of the callback function, button is a mouse button identifier (see table 3.4 on page 56), and action is either +PRESS+ or +RELEASE+ If cbfun is NULL, any previously selected callback function will be deselected. Return values none Description The function selects which function to be called upon a mouse button event. A window has to be opened for this function to have any effect. Notes Mouse button events are recorded continuously, but only reported when glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers is called. +MOUSE_BUTTON_LEFT+ is equal to +MOUSE_BUTTON_1+ +MOUSE_BUTTON_RIGHT+ is equal to +MOUSE_BUTTON_2+ +MOUSE_BUTTON_MIDDLE+ is equal to +MOUSE_BUTTON_3+
[Function]
set-mouse-pos xpos ypos => resultParameters xpos Horizontal position of the mouse. ypos Vertical position of the mouse. Description The function changes the position of the mouse. If the cursor is visible (not disabled), the cursor will be moved to the specified position, relative to the upper left corner of the window client area. If the cursor is hidden (disabled), only the mouse position that is reported by GLFW is changed.
[Function]
set-mouse-pos-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called every time the mouse is moved. The function should have the following C language prototype: void GLFWCALL functionname( int x, int y ); Where functionname is the name of the callback function, and x and y are the mouse coordinates (see glfw::GetMousePos for more information on mouse coordinates). If cbfun is NULL, any previously selected callback function will be deselected. Return values none Description The function selects which function to be called upon a mouse motion event. A window has to be opened for this function to have any effect. Notes Mouse motion events are recorded continuously, but only reported when glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers is called.
[Function]
set-mouse-wheel pos => resultParameters pos Position of the mouse wheel. Description The function changes the position of the mouse wheel.
[Function]
set-mouse-wheel-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called every time the mouse wheel is moved. The function should have the following C language prototype: void GLFWCALL functionname( int pos ); Where functionname is the name of the callback function, and pos is the mouse wheel position. If cbfun is NULL, any previously selected callback function will be deselected. Return values none Description The function selects which function to be called upon a mouse wheel event. A window has to be opened for this function to have any effect. Notes Mouse wheel events are recorded continuously, but only reported when glfw::PollEvents, glfw::WaitEvents or glfw::SwapBuffers is called.
[Function]
set-time time => resultParameters time Time (in seconds) that the timer should be set to. Description The function sets the current time of the high precision timer to the specified time. Subsequent calls to glfw::GetTime will be relative to this time. The time is given in seconds.
[Function]
set-window-close-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called when a user requests that the window should be closed, typically by clicking the window close icon (e.g. the cross in the upper right corner of a window under Microsoft Windows). The function should have the following C language prototype: int GLFWCALL functionname( void ); Where functionname is the name of the callback function. The return value of the callback function indicates wether or not the window close action should continue. If the function returns GL_TRUE, the window will be closed. If the function returns GL_FALSE, the window will not be closed. If cbfun is NULL, any previously selected callback function will be deselected. If you declare your callback as returning glfw:boolean, you can use t and nil as return types. Description The function selects which function to be called upon a window close event. A window has to be opened for this function to have any effect. Notes Window close events are recorded continuously, but only reported when glfwPollEvents, glfwWaitEvents or glfwSwapBuffers is called. The OpenGL™ context is still valid when this function is called. Note that the window close callback function is not called when glfwCloseWindow is called, but only when the close request comes from the window manager. Do not call glfwCloseWindow from a window close callback function. Close the window by returning GL_TRUE from the function.
[Function]
set-window-pos x y => resultParameters x Horizontal position of the window, relative to the upper left corner of the desktop. y Vertical position of the window, relative to the upper left corner of the desktop. Return values none Description The function changes the position of an opened window. It does not have any effect on a fullscreen window.
[Function]
set-window-refresh-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called when the window client area needs to be refreshed. The function should have the following CFFI prototype: (cffi:defcallback callback-name :void ((width :int) (height :int)) .. body ..) Where callback is the name of the callback function. If cbfun is the null-pointer, any previously selected callback function will be deselected. Description The function selects which function to be called upon a window refresh event, which occurs when any part of the window client area has been damaged, and needs to be repainted (for instance, if a part of the window that was previously occluded by another window has become visible). A window has to be opened for this function to have any effect. Notes Window refresh events are recorded continuously, but only reported when glfwPollEvents, glfwWaitEvents or glfwSwapBuffers is called.
[Function]
set-window-size width height => resultParameters width Width of the window. height Height of the window. Return values none Description The function changes the size of an opened window. The width and height parameters denote the size of the client area of the window (i.e. excluding any window borders and decorations). If the window is in fullscreen mode, the video mode will be changed to a resolution that closest matches the width and height parameters (the number of color bits will not be changed). Notes The OpenGL™ context is guaranteed to be preserved after calling glfwSetWindowSize, even if the video mode is changed.
[Function]
set-window-size-callback cbfun => resultParameters cbfun Pointer to a callback function that will be called every time the window size changes. The function should have the following C language prototype: void GLFWCALL functionname( int width, int height ); Where functionname is the name of the callback function, and width and height are the dimensions of the window client area. If cbfun is NULL, any previously selected callback function will be deselected. Return values none Description The function selects which function to be called upon a window size change event. A window has to be opened for this function to have any effect. Notes Window size changes are recorded continuously, but only reported when glfwPollEvents, glfwWaitEvents or glfwSwapBuffers is called.
[Function]
set-window-title title => resultParameters title Pointer to a null terminated ISO 8859-1 (8-bit Latin 1) string that holds the title of the window. Description The function changes the title of the opened window. Notes The title property of a window is often used in situations other than for the window title, such as the title of an application icon when it is in iconified state.
[Function]
signal-cond cond => resultParameters cond A condition variable object handle. Description The function restarts one of the threads that are waiting on the condition variable cond. If no threads are waiting on cond, nothing happens. If several threads are waiting on cond, exactly one is restarted, but it is not specified which. Notes When several threads are waiting for the condition variable, which thread is started depends on operating system scheduling rules, and may vary from system to system and from time to time.
[Function]
sleep time => resultParameters time Time, in seconds, to sleep. Description The function puts the calling thread to sleep for the requested period of time. Only the calling thread is put to sleep. Other threads within the same process can still execute. Notes There is usually a system dependent minimum time for which it is possible to sleep. This time is generally in the range 1 ms to 20 ms, depending on thread sheduling time slot intervals etc. Using a shorter time as a parameter to glfw::Sleep can give one of two results: either the thread will sleep for the minimum possible sleep time, or the thread will not sleep at all (glfw::Sleep returns immediately). The latter should only happen when very short sleep times are specified, if at all.
[Function]
swap-buffers => resultThe function swaps the back and front color buffers of the window. If +AUTO_POLL_EVENTS+ is enabled (which is the default), glfwPollEvents is called before swapping the front and back buffers.
[Function]
swap-interval interval => resultParameters interval Minimum number of monitor vertical retraces between each buffer swap performed by glfwSwapBuffers. If interval is zero, buffer swaps will not be synchronized to the vertical refresh of the monitor (also known as ’VSync off’). Description The function selects the minimum number of monitor vertical retraces that should occur between two buffer swaps. If the selected swap interval is one, the rate of buffer swaps will never be higher than the vertical refresh rate of the monitor. If the selected swap interval is zero, the rate of buffer swaps is only limited by the speed of the software and the hardware. Notes This function will only have an effect on hardware and drivers that support user selection of the swap interval.
[Function]
terminate => resultThe function terminates GLFW. Among other things it closes the window, if it is opened, and kills any running threads. This function must be called before a program exits.
[Function]
unlock-mutex mutex => resultParameters mutex A mutex object handle. Description The function releases the lock of a locked mutex object.
[Function]
wait-cond cond mutex timeout => resultarameters cond A condition variable object handle. mutex A mutex object handle. timeout Maximum time to wait for the condition variable. The parameter can either be a positive time (in seconds), or +INFINITY+ Description The function atomically unlocks the mutex specified by mutex, and waits for the condition variable cond to be signaled. The thread execution is suspended and does not consume any CPU time until the condition variable is signaled or the amount of time specified by timeout has passed. If timeout is +INFINITY+ glfw::WaitCond will wait forever for cond to be signaled. Before returning to the calling thread, glfw::WaitCond automatically re-acquires the mutex. Notes The mutex specified by mutex must be locked by the calling thread before entrance to glfw::WaitCond. A condition variable must always be associated with a mutex, to avoid the race condition where a thread prepares to wait on a condition variable and another thread signals the condition just before the first thread actually waits on it.
[Function]
wait-events => resultDescription The function is used for waiting for events, such as user input and window resize events. Upon calling this function, the calling thread will be put to sleep until any event appears in the event queue. When events are ready, the events will be processed just as they are processed by glfwPollEvents. If there are any events in the queue when the function is called, the function will behave exactly like glfwPollEvents (i.e. process all messages and then return, without blocking the calling thread). Notes It is guaranteed that glfwWaitEvents will wake up on any event that can be processed by glfw::PollEvents. However, glfwWaitEvents may wake up on events that are not processed or reported by glfw::PollEvents too, and the function may behave differently on different systems. Do no make any assumptions about when or why glfw::WaitEvents will return.
[Function]
wait-thread id waitmode => resultParameters ID A thread identification handle, which is returned by glfw::CreateThread or glfw::GetThreadID. waitmode Can be either +WAIT+ or +NOWAIT+ Return values The function returns t if the specified thread died after the function was called, or the thread did not exist, in which case glfw::WaitThread will return immediately regardless of waitmode. The function returns nil if waitmode is +NOWAIT+ and the specified thread exists and is still running.
[Macro]
with-init declaration* statement* => resultCall glfw:init, execute forms and clean-up with glfw:terminate once finished. This makes a nice wrapper to an application higher-level form. Signals an error on failure to initialize. Wrapped in a block named glfw:with-init.Wraps forms in with-init, with-open-window. Passes through the other arguments to open-window.
[Macro]
with-lock-mutex mutex declaration* statement* => resultParameters mutex A mutex object handle. forms Body of code to execute Description This macro will acquire a lock on the selected mutex object using glfw::LockMutex and release it afterwards using glfw::UnlockMutex. So, forms will not execute until an exclusive lock is held. The lock is then released when the stack is unwound.Wraps forms such that there is an open window for them to execute in and cleans up the window afterwards. An error is signalled if there was an error opening the window. Takes the same parameters as open-window, with the addition of 'title' which will set the window title after opening. Wrapped in a block named glfw:with-open-window.
Acknowledgements
This documentation was prepared with DOCUMENTATION-TEMPLATE.