![]() |
Inheritance diagram for Gtk::CheckMenuItem:

Public Member Functions | |
| virtual | ~CheckMenuItem () |
| GtkCheckMenuItem* | gobj () |
| Provides access to the underlying C GtkObject. | |
| const GtkCheckMenuItem* | gobj () const |
| Provides access to the underlying C GtkObject. | |
| CheckMenuItem () | |
| CheckMenuItem (const Glib::ustring& label, bool mnemonic=false) | |
| void | set_active (bool state=true) |
| bool | get_active () const |
| void | toggled () |
| void | set_inconsistent (bool setting=true) |
| bool | get_inconsistent () const |
| void | set_draw_as_radio (bool draw_as_radio=true) |
| bool | get_draw_as_radio () const |
| Glib::SignalProxy0<void> | signal_toggled () |
| Glib::PropertyProxy<bool> | property_active () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy<bool> | property_inconsistent () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy<bool> | property_draw_as_radio () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
Protected Member Functions | |
| virtual void | draw_indicator_vfunc (GdkRectangle* area) |
| virtual void | on_toggled () |
Related Functions | |
| (Note that these are not member functions.) | |
| Gtk::CheckMenuItem* | wrap (GtkCheckMenuItem* object, bool take_copy=false) |
A check box indicating the state of the boolean value is displayed at the left side of the Gtk::MenuItem. Activating the Gtk::MenuItem toggles the value.
|
|
|
|
|
|
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gtk::MenuItem. Reimplemented in Gtk::RadioMenuItem. |
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gtk::MenuItem. Reimplemented in Gtk::RadioMenuItem. |
|
|
|
|
|
You rarely need to use properties because there are get_ and set_ methods for almost all of them.
|
|
|
You rarely need to use properties because there are get_ and set_ methods for almost all of them.
|
|
|
You rarely need to use properties because there are get_ and set_ methods for almost all of them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|