GNOME Bugzilla – Bug 491974
The documentation of the interface "g_main_context_iteration" does not completely describe it's functionality for the "may_block" parameter
Last modified: 2007-11-10 00:25:12 UTC
Documentation Section: http://library.gnome.org/devel/glib/unstable/glib-The-Main-Event-Loop.html#g-main-context-iteration This involves checking to see if any event sources are ready to be processed, then if no events sources are ready and may_block is TRUE, waiting for a source to become ready, then dispatching the highest priority events sources that are ready. Correct version: This involves checking to see if any event sources are ready to be processed, then if no events sources are ready and may_block is TRUE, waiting for a source to become ready, then dispatching the highest priority events sources that are ready. Otherwise, if may_block is FALSE sources are not waited to become ready, only those highest priority events sources will be dispatched (if any), that are ready at this given moment without further waiting. Other information: The detailed issue description can be found at: http://linuxtesting.org/results/report?num=D0014
2007-11-09 Matthias Clasen <mclasen@redhat.com> * glib/gmain.c (g_main_context_iteration): Improve the docs. (#491974, Areg Beketovski)