![]() |
![]() |
It may not be global and must be the first Gtk object created. It is a singleton so declaring more than one will simply access the first created.
Normal use of this class is in the main() function to give argc and argv to the gtk initialization. Widgets can use Gtk::Main::quit() to exit from the application.
The internals of the widget have been disguised as signals so that the user can easily connect using the same methods used throughout the widget interface.
Minimal gtkmm application is something like this:
int main(int argc, char *argv[]) { Gtk::Main kit(argc, argv); ... create some widgets ... kit.run(); }
Public Member Functions | |
Main (int* argc, char*** argv, bool set_locale=true) | |
Scans the argument vector, and strips off all parameters known to GTK+. | |
Main (int& argc, char**& argv, bool set_locale=true) | |
virtual | ~Main () |
Static Public Member Functions | |
Gtk::Main* | instance () |
Access to one global instance of Gtk::Main. | |
void | run () |
Start the event loop. | |
void | run (Window& window) |
Returns from the main loop when the window is closed. | |
void | quit () |
guint | level () |
void | iteration (bool blocking=true) |
bool | events_pending () |
RunSig& | signal_run () |
Run signal. | |
QuitSig& | signal_quit () |
Quit signal You can connect signal handlers to invoke actions when Gtk::Main::quit() has been called. | |
KeySnooperSig& | signal_key_snooper () |
KeySnooper signal Allows you to channel keypresses to a signal handler without registering with the widget. | |
void | init_gtkmm_internals () |
Protected Member Functions | |
Main () | |
void | init (int* argc, char*** argv, bool set_locale) |
virtual void | run_impl () |
virtual void | quit_impl () |
virtual guint | level_impl () |
virtual void | iteration_impl (bool blocking) |
virtual bool | events_pending_impl () |
virtual void | on_window_hide () |
Static Protected Attributes | |
RunSig | signal_run_ |
QuitSig | signal_quit_ |
KeySnooperSig | signal_key_snooper_ |
|
Scans the argument vector, and strips off all parameters known to GTK+. Your application may then handle the remaining arguments. Note: The argument strings themself won't be modified, although the pointers to them might change. This makes it possible to create your own argv of string literals, which have the type 'const char[]' in standard C++. (You might need to use const_cast<>, though.) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Access to one global instance of Gtk::Main.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Returns from the main loop when the window is closed. When using this override, you should not use Gtk::Main::quit() to close the application, but just call hide() on your Window class. |
|
Start the event loop. This begins the event loop which handles events. No events propagate until this has been called. It may be called recursively to popup dialogs
|
|
|
|
KeySnooper signal Allows you to channel keypresses to a signal handler without registering with the widget.
|
|
Quit signal You can connect signal handlers to invoke actions when Gtk::Main::quit() has been called.
Note that main loops can be nested by calling Gtk::Main::run() recursively, therefore receiving this signal doesn't necessarily mean the application is about to be terminated. If you want to receive a signal only when the last main loop quits, call connect() with bool thisclass::mymethod() { return false; } Gtk::Main::signal_quit().connect(SigC::slot(this, &thisclass::mymethod));
|
|
Run signal.
|
|
|
|
|
|
|