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

Public Member Functions | |
| virtual | ~ComboBox () |
| GtkComboBox* | gobj () |
| Provides access to the underlying C GtkObject. | |
| const GtkComboBox* | gobj () const |
| Provides access to the underlying C GtkObject. | |
| ComboBox (const Glib::RefPtr<TreeModel>& model) | |
| void | set_wrap_width (int width) |
| void | set_row_span_column (int row_span) |
| void | set_column_span_column (int column_span) |
| int | get_active_row_number () const |
| TreeModel::iterator | get_active () |
| TreeModel::const_iterator | get_active () const |
| void | set_active (int index) |
| void | set_active (const TreeModel::iterator& iter) |
| void | unset_active () |
| Glib::RefPtr<TreeModel> | get_model () |
| Glib::RefPtr<const TreeModel> | get_model () const |
| Glib::PropertyProxy<int> | property_wrap_width () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy<int> | property_row_span_column () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy<int> | property_column_span_column () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy<int> | property_active () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::SignalProxy0<void> | signal_changed () |
Protected Member Functions | |
| virtual void | on_changed () |
Related Functions | |
| (Note that these are not member functions.) | |
| Gtk::ComboBox* | wrap (GtkComboBox* object, bool take_copy=false) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gtk::Bin. Reimplemented in Gtk::ComboBoxEntry. |
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gtk::Bin. Reimplemented in Gtk::ComboBoxEntry. |
|
|
|
|
|
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.
|
|
|
You rarely need to use properties because there are get_ and set_ methods for almost all of them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|