|
|
|
@ -33,8 +33,10 @@ information. |
|
|
|
|
|
|
|
|
|
GLFW needs to communicate regularly with the window system both in order to |
|
|
|
|
receive events and to show that the application hasn't locked up. Event |
|
|
|
|
processing must be done regularly while you have visible windows and is normally |
|
|
|
|
done each frame after [buffer swapping](@ref buffer_swap). |
|
|
|
|
processing must be done regularly while you have any windows and is normally |
|
|
|
|
done each frame after [buffer swapping](@ref buffer_swap). Even when you have |
|
|
|
|
no windows, event polling needs to be done in order to receive monitor |
|
|
|
|
connection events. |
|
|
|
|
|
|
|
|
|
There are two functions for processing pending events. @ref glfwPollEvents, |
|
|
|
|
processes only those events that have already been received and then returns |
|
|
|
|