You may consider it a dirty word, but multiple inheritance may be useful
here. You may be able to use the Publisher class as a mix in class to get
it's signal behaviour without having to change the rest of pygtk (which
could potentially break a number of other programs). Something like this:
class MyDerivedWidget(GtkSomething, Publisher):
...
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On 26 Oct 1999, Bernhard Herzog wrote:
> > Hmmm... Another idea... But maybe include it (Publisher class)
> > into pygtk and then GtkObject could derive from Publisher?
>
> Hmm. I'm not sure whether that would be a good idea. gtk and pygtk are
> (just) toolkits, whereas Sketch's signal mechanism tends more towards an
> application framework, so I think it complements pygtk but perhaps
> shouldn't be an integral part of it.
>
> In Sketch at least, I use it more for internal communication between
> e.g. the document and its views to update the views when the document
> changes, and rarely directly with GTK widgets.
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
