Prevents gtk_init(), gtk_init_check(), gtk_init_with_args() and gtk_parse_args() from automatically calling setlocale (LC_ALL, ""). You would want to use this function if you wanted to set the locale for your program to something other than the user's locale, or if you wanted to set different values for different locale categories. Most programs should not need to call this function.
Processes a single GDK event. This is public only to allow filtering of events between GDK and GTK+. You will not usually need to call this function directly. While you should not call this function directly, you might want to know how exactly events are handled. So here is what this function does with
Checks if any events are pending. This can be used to update the GUI and invoke timeouts etc. while doing some time intensive computation.
Warning gtk_exit is deprecated and should not be used in newly-written code. Use the standard exit() function instead. Terminates the program and returns the given exit code to the caller. This function will shut down the GUI and free all resources allocated for GTK+.
Obtains a copy of the event currently being processed by GTK+. For example, if you get a "clicked" signal from GtkButton, the current event will be the GdkEventButton that triggered the "clicked" signal. The returned event must be freed with gdk_event_free(). If there is no current event, the function returns NULL.
If there is a current event and it has a state field, place that state field in state and return TRUE, otherwise return FALSE.
If there is a current event and it has a timestamp, return that timestamp, otherwise return GDK_CURRENT_TIME.
Returns the PangoLanguage for the default language currently in effect. (Note that this can change over the life of an application.) The default language is derived from the current locale. It determines, for example, whether GTK+ uses the right-to-left or left-to-right text direction. This function is equivalent to pango_language_get_default(). See that function for details.
If event is NULL or the event was not associated with any widget, returns NULL, otherwise returns the widget that received the event originally.
Returns a GOptionGroup for the commandline arguments recognized by GTK+ and GDK. You should add this group to your GOptionContext with g_option_context_add_group(), if you are using g_option_context_parse() to parse your commandline arguments. Since 2.6
Makes widget the current grabbed widget. This means that interaction with other widgets in the same application is blocked and mouse as well as keyboard events are delivered to this widget. If widget is not sensitive, it is not set as the current grabbed widget and this function does nothing.
Queries the current grab of the default window group. Queries the current grab of the default window group.
Removes the grab from the given widget. You have to pair calls to gtk_grab_add() and gtk_grab_remove(). If widget does not have the grab, this function does nothing.
Call this function before using any other GTK+ functions in your GUI applications.
Call this function before using any other GTK+ functions in your GUI applications. It will initialize everything needed to operate the toolkit and parses some standard command line options. argc and argv are adjusted accordingly so your own code will never see those standard arguments. Since 2.18, GTK+ calls signal (SIGPIPE, SIG_IGN) during initialization, to ignore SIGPIPE signals, since these are almost never wanted in graphical applications. If you do need to handle SIGPIPE for some reason, reset the handler after gtk_init(), but notice that other libraries (e.g. libdbus or gvfs) might do similar things. Note
Warning gtk_init_add is deprecated and should not be used in newly-written code. This function is going to be removed in GTK+ 3.0 Registers a function to be called when the mainloop is started.
This function does the same work as gtk_init() with only a single change: It does not terminate the program if the GUI can't be initialized. Instead it returns FALSE on failure. This way the application can fall back to some other means of communication with the user - for example a curses or command line interface.
This initiates GtkD to supports multi threaded programs. read full documantation at http://gtk.org/faq/#AEN482 from the FAQ: "There is a single global lock that you must acquire with gdk_threads_enter() before making any GDK calls, and release with gdk_threads_leave() afterwards throughout your code." This is to be used on any call to GDK not executed from the main thread.
This function does the same work as gtk_init_check(). Additionally, it allows you to add your own commandline options, and it automatically generates nicely formatted --help output. Note that your program will be terminated after writing out the help output. Since 2.6
Warning gtk_input_add_full has been deprecated since version 2.4 and should not be used in newly-written code. Use g_io_add_watch_full() instead. Registers a function to be called when a condition becomes true on a file descriptor.
Warning gtk_input_remove has been deprecated since version 2.4 and should not be used in newly-written code. Use g_source_remove() instead. Removes the function with the given id.
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.
Runs a single iteration of the mainloop. If no events are available either return or block dependent on the value of blocking.
Installs a key snooper function, which will get called on all key events before delivering them normally.
Removes the key snooper function with the given id.
Asks for the current nesting level of the main loop. This can be useful when calling gtk_quit_add().
Parses command line arguments, and initializes global attributes of GTK+, but does not actually open a connection to a display. (See gdk_display_open(), gdk_get_display_arg_name()) Any arguments used by GTK+ or GDK are removed from the array and argc and argv are updated accordingly. There is no need to call this function explicitely if you are using gtk_init(), or gtk_init_check().
Sends an event to a widget, propagating the event to parent widgets if the event remains unhandled. Events received by GTK+ from GDK normally begin in gtk_main_do_event(). Depending on the type of event, existence of modal dialogs, grabs, etc., the event may be propagated; if so, this function is used. gtk_propagate_event() calls gtk_widget_event() on each widget it decides to send the event to. So gtk_widget_event() is the lowest-level function; it simply emits the "event" and possibly an event-specific signal on a widget. gtk_propagate_event() is a bit higher-level, and gtk_main_do_event() is the highest level. All that said, you most likely don't want to use any of these functions; synthesizing events is rarely needed. Consider asking on the mailing list for better ways to achieve your goals. For example, use gdk_window_invalidate_rect() or gtk_widget_queue_draw() instead of making up expose events.
Makes the innermost invocation of the main loop return when it regains control.
Warning gtk_quit_add is deprecated and should not be used in newly-written code. This function is going to be removed in GTK+ 3.0 Registers a function to be called when an instance of the mainloop is left.
Warning gtk_quit_add_destroy is deprecated and should not be used in newly-written code. This function is going to be removed in GTK+ 3.0 Trigger destruction of object in case the mainloop at level main_level is quit.
Warning gtk_quit_add_full is deprecated and should not be used in newly-written code. This function is going to be removed in GTK+ 3.0 Registers a function to be called when an instance of the mainloop is left. In comparison to gtk_quit_add() this function adds the possibility to pass a marshaller and a function to be called when the quit handler is freed. The former can be used to run interpreted code instead of a compiled function while the latter can be used to free the information stored in data (while you can do this in function as well)... So this function will mostly be used by GTK+ wrappers for languages other than C.
Warning gtk_quit_remove is deprecated and should not be used in newly-written code. This function is going to be removed in GTK+ 3.0 Removes a quit handler by its identifier.
Warning gtk_quit_remove_by_data is deprecated and should not be used in newly-written code. This function is going to be removed in GTK+ 3.0 Removes a quit handler identified by its data field.
Runs the main loop until gtk_main_quit() is called. You can nest calls to gtk_main(). In that case gtk_main_quit() will make the innermost invocation of the main loop return.
Warning gtk_set_locale has been deprecated since version 2.24 and should not be used in newly-written code. Use setlocale() directly Initializes internationalization support for GTK+. gtk_init() automatically does this, so there is typically no point in calling this function. If you are calling this function because you changed the locale after GTK+ is was initialized, then calling this function may help a bit. (Note, however, that changing the locale after GTK+ is initialized may produce inconsistent results and is not really supported.) In detail - sets the current locale according to the program environment. This is the same as calling the C library function setlocale (LC_ALL, "") but also takes care of the locale specific setup of the windowing system used by GDK.
Description Before using GTK+, you need to initialize it; initialization connects to the window system display, and parses some standard command line arguments. The gtk_init() function initializes GTK+. gtk_init() exits the application if errors occur; to avoid this, use gtk_init_check(). gtk_init_check() allows you to recover from a failed GTK+ initialization - you might start up your application in text mode instead. Like all GUI toolkits, GTK+ uses an event-driven programming model. When the user is doing nothing, GTK+ sits in the main loop and waits for input. If the user performs some action - say, a mouse click - then the main loop "wakes up" and delivers an event to GTK+. GTK+ forwards the event to one or more widgets. When widgets receive an event, they frequently emit one or more signals. Signals notify your program that "something interesting happened" by invoking functions you've connected to the signal with g_signal_connect(). Functions connected to a signal are often termed callbacks. When your callbacks are invoked, you would typically take some action - for example, when an Open button is clicked you might display a GtkFileSelectionDialog. After a callback finishes, GTK+ will return to the main loop and await more user input. It's OK to use the GLib main loop directly instead of gtk_main(), though it involves slightly more typing. See GMainLoop in the GLib documentation.