James> class _HEntry(gtk.Entry):
James> def __init__(self):
James> gobject.GObject.__init__(self)
James> self.set_name("_history_")
James> gobject.type_register(_HEntry)
James> Note the gobject.type_register() call, and chaining to
James> GObject.__init__ rather than gtk.Entry.__init__. If you look at
James> _HEntry.__gtype__, it should be for This way, the signals will be
James> added to your new type rather than GtkEntry. This will also
James> change the type name used in the gtkrc file. The type name is
James> generated from the full class name (module.class), with dots
James> replaced with plus signs (because Tim doesn't want to make dots
James> valid in type names).
Thanks, I never would have guessed that. How come there is no need to chain
through gtk.Entry.__init__?
James> Does the above comments help?
Yes, thanks. (My other alternative was to hang my new signals off
gtk.Widget...)
Skip
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
