On Wed, 26 Sep 2001, Christian Robottom Reis wrote:
> On Fri, 21 Sep 2001, Skip Montanaro wrote:
>
> >
> > Matt> This raises a question - do we want to do gtk_widget_set_name by
> > Matt> default on extended classes?
> >
> > I don't think that's necessary, since its available to the application
> > programmer. Besides, that names a widget instance, not a widget class,
> > right?
>
> Yes, but we set names to the class names by default for instances that
> don't do set_name. Matt, I'm not so sure; what would happen if we
> _didn't_?
Actually, if set_name() hasn't been called, the type name is used instead.
The "widget_style ..." lines match a dotted path of widget names (or
classes when the names aren't present); eg. GtkWindow.hbox.mylabel.
The "widget_class ..." lines are like widget_style, but match on
classnames always (ignoring names assigned to widgets.
The "class ..." lines match just the classname of the widget (and I think
they also follow inheritance, so a "class" style set on GtkBox would
affect GtkHBox.
Libglade sets the widget name on all widgets it creates to match what is
in the .glade file.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
