#include <widget.h>
Inheritance diagram for Gnome::Canvas::Widget:

Public Member Functions | |
| virtual | ~Widget () |
| GnomeCanvasWidget * | gobj () |
| Provides access to the underlying C GtkObject. | |
| const GnomeCanvasWidget * | gobj () const |
| Provides access to the underlying C GtkObject. | |
| Widget (Group &parent, double x, double y, Gtk::Widget &w) | |
| Widget (Group &parent) | |
| Glib::PropertyProxy< Gtk::Widget > | property_widget () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< double > | property_x () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< double > | property_y () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< double > | property_width () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< double > | property_height () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< Gtk::AnchorType > | property_anchor () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
| Glib::PropertyProxy< bool > | property_size_pixels () |
| You rarely need to use properties because there are get_ and set_ methods for almost all of them. | |
Related Functions | |
| (Note that these are not member functions.) | |
| Gnome::Canvas::Widget * | wrap (GnomeCanvasWidget *object, bool take_copy=false) |
|
|
|
|
||||||||||||||||||||
|
|
|
|
|
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gnome::Canvas::Item. |
|
|
Provides access to the underlying C GtkObject.
Reimplemented from Gnome::Canvas::Item. |
|
|
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.
|
|
|
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.3.7