Richard Fish <[EMAIL PROTECTED]> writes: > I think until we are able to pass the original python object to > signal handlers, we are better off just not having user-created > attributes available to the signal handlers. I think I agree with this. Fortunately, there are other ways of sharing data with signal callbacks, such as passing mutable objects to signal_connect, or using class methods as objects (which gives you `self' to access.) Otherwise, there really should be some way of achieving 1:1 mapping between Python and Gtk objects. I'll think about it some more. To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
- [pygtk] Inheriting from Gtk classes broken? Hrvoje Niksic
- Re: [pygtk] Inheriting from Gtk classes broke... Richard Fish
- Re: [pygtk] Inheriting from Gtk classes broke... Richard Fish
- Re: [pygtk] Inheriting from Gtk classes broke... Richard Fish
- Re: [pygtk] Inheriting from Gtk classes b... Hrvoje Niksic
- Re: [pygtk] Inheriting from Gtk classes broke... James Henstridge
- Re: [pygtk] Inheriting from Gtk classes broke... Richard Fish
- Re: [pygtk] Inheriting from Gtk classes b... Hrvoje Niksic
- Re: [pygtk] Inheriting from Gtk classes broke... Aaron Optimizer Digulla
- Re: [pygtk] Inheriting from Gtk classes broke... Richard Fish
- Re: [pygtk] Inheriting from Gtk classes broke... Aaron Optimizer Digulla
- Re: [pygtk] Inheriting from Gtk classes b... Hrvoje Niksic
- Re: [pygtk] Inheriting from Gtk classes b... Richard Fish
