GPipe context handler for GLFW

Opaque handle representing the initialized GLFW library.

To get started quickly try defaultHandleConfig and defaultWindowConfig.

     import Graphics.GPipe
     import qualified Graphics.GPipe.Context.GLFW as GLFW

     runContextT GLFW.defaultHandleConfig $ do
         win <- newWindow (WindowFormatColorDepth RGB8 Depth16) (GLFW.defaultWindowConfig "OpenGL Graphics")
         -- Do GPipe things here

Opaque handle representing a, possibly closed, internal Context. You'll typically deal with GPipe's Window instead of this one.

Default GLFW handle configuration.

• Print any errors that GLFW emits.
• Automatically process GLFW events after every buffer swap.

Default window configuration for a small window on any monitor with the given title.

Implementation specific context handler parameters, eg error handling and event processing policies

Configuration for a new GLFW window and associated OpenGL context.

Type to describe the waiting or polling style of event processing supported by GLFW.

• Recommended reading: Event Processing section of the GLFW Input Guide at http://www.glfw.org/docs/latest/input_guide.html#events.

IO exception thrown when GLFW library initialization fails.

IO Exception thrown when GLFW window creation fails.

IO Exception thrown when attempting to create a new window using GLFW hints which GPipe manages.

Process GLFW and GPipe events according to the given EventPolicy in a loop.

Use case: Call mainloop in multithreaded applications which do GPipe rendering off of the main thread, but which do not otherwise need additional control over the main thread. For less complex applications use automatic event processing configured via HandleConfig.

• Must be called on the main thread.
• The loop will run until windowShouldClose is true for the all Windows created by the same ContextHandler, or all the Windows have been deleted.
• To indicate a window should close use setWindowShouldClose in Graphics.GPipe.Context.GLFW.Wrapped.

Process GLFW and GPipe events according to the given EventPolicy.

Use case: Call mainstep as part of a custom engine loop in multithreaded applications which do GPipe rendering off of the main thread. Use mainloop for less complex applications.

• Must be called on the main thread.
• Can be called with any window you've created and not yet deleted.
• If GPipe can't find the window you passed in, returns Nothing.