In more complex Tkinter projects, that rule does not seem to be followed.
Usually you may want to subclass an existing widget to get some special
behaviour. In both pygtk and Tkinter cases, subclassing a widget is the
easiest way of achieving this.
I don't really have any specific recommendations to do with this. The
main one is to not override any of the methods that are straight wrappers
for C functions. If the equivalent C function is called on the object,
the method of your derived class will not be called, so you can't rely on
it.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Fri, 25 Feb 2000, Moshe Zadka wrote:
> My previous experience in Python GUI toolkits was with Tkinter. In
> Tkinter, the official advice was ``don't inherit from anything except
> Frame''. I wonder what the official advice about PyGTK is.
>
> Is it considered politically correct to inherit from Gtk[VH]Box?
> Are there any caveats?
>
> Thanks in advance.
> --
> Moshe Zadka <[EMAIL PROTECTED]>.
> INTERNET: Learn what you know.
> Share what you don't.
>
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
