A wrapper for the common usage of Threads.addIdleFull assigning the default priority, G_PRIORITY_DEFAULT_IDLE
Adds a function to be called whenever there are no higher priority events pending. If the function returns FALSE it is automatically removed from the list of event sources and will not be called again.
A wrapper for the common usage of Threads.addTimeoutFull assigning the default priority, G_PRIORITY_DEFAULT
Sets a function to be called at regular intervals holding the GDK lock, with the given priority. The function is called repeatedly until it returns FALSE, at which point the timeout is automatically destroyed and the function will not be called again. The notify function is called when the timeout is destroyed. The first call to the function will be at the end of the first interval.
A wrapper for the common usage of Threads.addTimeoutSecondsFull assigning the default priority, G_PRIORITY_DEFAULT
A variant of Threads.addTimeoutFull with second-granularity. See Timeout.addSecondsFull for a discussion of why it is a good idea to use this function if you don’t need finer granularity.
This function marks the beginning of a critical section in which GDK and GTK+ functions can be called safely and without causing race conditions. Only one thread at a time can be in such a critial section.
Initializes GDK so that it can be used from multiple threads in conjunction with Threads.enter and Threads.leave.
Leaves a critical region begun with Threads.enter.
Allows the application to replace the standard method that GDK uses to protect its data structures. Normally, GDK creates a single glib.Mutex that is locked by Threads.enter, and released by Threads.leave; using this function an application provides, instead, a function enter_fn that is called by Threads.enter and a function leave_fn that is called by Threads.leave.
Undocumented in source.