From 728a088cd7d8fe5884ed1e30f8dadf1f73cf6e96 Mon Sep 17 00:00:00 2001 From: Camilla Berglund Date: Fri, 18 Mar 2016 12:08:43 +0100 Subject: [PATCH] Fix event processing guide section --- docs/input.dox | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/input.dox b/docs/input.dox index 89587d3d..c426e887 100644 --- a/docs/input.dox +++ b/docs/input.dox @@ -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