#include <druid.h>
Inheritance diagram for Gnome::UI::Druid:

Public Types | |
| typedef DruidPage | Page |
Public Member Functions | |
| virtual | ~Druid () |
| GnomeDruid * | gobj () |
| Provides access to the underlying C GtkObject. | |
| const GnomeDruid * | gobj () const |
| Provides access to the underlying C GtkObject. | |
| Druid () | |
| void | set_buttons_sensitive (bool back_sensitive, bool next_sensitive, bool cancel_sensitive, bool help_sensitive) |
| void | set_show_finish (bool show_finish=true) |
| void | set_show_help (bool show_help=true) |
| void | prepend_page (const DruidPage &page) |
| void | insert_page (const DruidPage &back_page, const DruidPage &page) |
| void | append_page (const DruidPage &page) |
| void | set_page (const DruidPage &page) |
| Glib::SignalProxy0< void > | signal_cancel () |
| Glib::SignalProxy0< void > | signal_help () |
| Glib::PropertyProxy< bool > | property_show_finish () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy_ReadOnly< bool > | property_show_finish () const |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< bool > | property_show_help () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy_ReadOnly< bool > | property_show_help () const |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
Protected Member Functions | |
| virtual void | on_cancel () |
| virtual void | on_help () |
Related Functions | |
| (Note that these are not member functions.) | |
| Gnome::UI::Druid * | wrap (GnomeDruid *object, bool take_copy=false) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gtk::Container. |
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gtk::Container. |
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
1.4.1