On Thu, 2004-08-05 at 06:23, Sridhar R wrote: > Graham Ashton <[EMAIL PROTECTED]> wrote: > > On Wed, 2004-08-04 at 01:40, Sridhar R wrote: > > > Graham Ashton <[EMAIL PROTECTED]> wrote: > > > > > > > If anybody wants a really simple implementation to this kind of wrapper > > > > class feel free to rip off the WidgetWrapper class hierarchy that I've > > > > knocked up here (it's tiny): > > > > > > > > http://cvs.sourceforge.net/viewcvs.py/bandsaw/bandsaw/src/bandsaw.py?view=markup > > > > > > But the signal connection part is a little bit weak. How do you > > > connect signals to some deeply nested widgets in that hierarchy? > > > > What do you mean by deeply nested? > > child of child of .. the toplevel widget. (may be wrong terminology).
Thanks. I don't understand why you think it doesn't work. signal_autoconnect() does the nested widgets for you. Or am I missing the point? -- Graham Ashton _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
