On 1 September 2010 18:39, Jason Heeris <[email protected]> wrote:
> The latter approach isn't actually a bad idea, although it involves the > extra typical GObject boilerplate... > Actually, the other problem with that approach is that I don't get to use the underlying properties and notifications for free. I'd need to reproduce the properties in my own GObject subclass, connect to the notifications in my wrapper class and emit any changes back out. Since I don't really need any of that right now, it's not a big deal though. — Jason
_______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
