All symbols of Gtk+ binding in cl-gtk2 reside in gtk package.

Gtk+ Main loop
**************

Gtk+ is an event-driven toolkit and it naturally is built around the event dispatching loop. The Gtk+ Main loop is a GLib Main loop. This section describes Gtk+-specific usage of the main loop.

Gtk+ main loop is run in a background thread that is launched by ensure-gtk-main (however it is also possible to launch Gtk+ main loop with gtk-main that does not spawn threads). This allows interactive development: while the Gtk+ thread is blocked by waiting for events or processing them, REPL thread is alive.

Gtk+ is not thread-safe, but thread-aware. This means that any access to Gtk+ from the thread different from the thread running the main loop must be explicitly synchronized with Gtk+. There are two ways to call Gtk+ from another thread:

  * Use gdk_threads_enter, gdk_threads_leave. This is unsupported at this time on cl-gtk2.

  * Use within-main-loop and related macros and functions.

gtk-main

     (gtk-main)

This function runs the main loop and returns when the main loop is terminated. (see gtk-main-quit and ensure-gtk-main)

gtk-main-quit

     (gtk-main-quit)

This function causes the main loop to terminate and causes gtk-main to return.

ensure-gtk-main

     (ensure-gtk-main)

This function ensures that the Gtk+ main loop is started in background thread. If the loop has not been started or if had been terminated, restarts the background thread.

join-main-thread

     (join-main-thread)

This function waits for the background thread that runs the Gtk+ main loop to quit.

gtk-main-iteration

     (gtk-main-iteration) => boolean

Runs a single iteration of the mainloop. If no events are waiting to be processed Gtk+ will block until the next event is noticed. If you don't want to block look at gtk-main-iteration-do or check if any events are pending with gtk-events-pending first.

Returns a boolean that is true if gtk-main-quit has been called for the innermost mainloop.

gtk-main-iteration-do

     (gtk-main-iteration-do blocking) => boolean

BLOCKING
     True if you want Gtk+ to block if no events are pending

Runs a single iteration of the mainloop. If no events are available either return or block dependent on the value of BLOCKING.

Returns a boolean that is true if gtk-main-quit has been called for the innermost mainloop.

gtk-events-pending

     (gtk-events-pending) => boolean

Checks if any events are pending. This can be used to update the GUI and invoke timeouts etc. while doing some time intensive computation. Note that this is not the best way to have a responsive GUI - it is usually better to do work in background thread.

gtk-main-add-timeout

     (gtk-main-add-timeout milliseconds function &key (priority +g-priority-default+)) => source-id

MILLISECONDS
     An integer specifying the time between calls to the function, in milliseconds (1/1000ths of a second.)

FUNCTION
     The function to call periodically. This function accepts zero arguments and returns a boolean.

PRIORITY
     An integer specifying the priority of the timeout. Typically this will be in the range between +g-priority-default+ and +g-priority-high+.

SOURCE-ID
     An integer identifier of GLib event source.

Registers a FUNCTION to be called periodically. The function will be called repeatedly after once per MILLISECONDS until it returns False at which point the timeout is destroyed and will not be called again. Timeout can also be removed by passing SOURCE-ID to g-source-remove.
within-main-loop

     (within-main-loop &body body)

Schedules the BODY to be evaluated within the main loop. Expression inside BODY are run inside the main loop, so they can call any Gtk+ functions. This expression may be evaluated in any thread.

Returns immediately. If the main loop was not started, uses ensure-gtk-main to start it.

within-main-loop-and-wait

     (within-main-loop-and-wait &body body) => results

Schedules the BODY to be evaluated within the main loop. Expression inside BODY are run inside the main loop, so they can call any Gtk+ functions. This expression may be evaluated in any thread.

Returns the values produced by evaluating BODY. If the evaluation of BODY results in unhandled error, the gtk-call-aborted error condition is signaled.

If the main loop was not started, uses ensure-gtk-main to start it.

call-from-gtk-main-loop

     (call-from-gtk-main-loop function &key (priority +g-priority-default-idle+))

FUNCTION
     The function to be called. Accepts zero arguments.

PRIORITY
     An integer specifying the priority of the call.

Schedules the FUNCTION to be called within the main loop. FUNCTION is evaluated inside the main loop, so it can call any Gtk+ functions. This function may be called from any thread.

If the main loop was not started, uses ensure-gtk-main to start it.

call-within-main-loop-and-wait

     (call-from-gtk-main-loop-and-wait function)

FUNCTION
     The function to be called. Accepts zero arguments and returns zero, one or more values.

Schedules the FUNCTION to be called within the main loop. FUNCTION is evaluated inside the main loop, so it can call any Gtk+ functions. This function may be called from any thread.

Returns the values produced by calling FUNCTION. If the evaluation of FUNCTION results in unhandled error, the gtk-call-aborted error condition is signaled.

If the main loop was not started, uses ensure-gtk-main to start it.

gtk-call-aborted

A condition inheriting from error that is used to signal the fact that the evaluation of expression or function in main loop by within-main-loop, within-main-loop-and-wait, call-from-gtk-main-loop, call-within-main-loop-and-wait was interrupted by error.

gtk-call-aborted-condition

Returns the error that caused call to aborted.