On Thu, 8 Nov 2012 10:05:12 -0500 Ian Ward <[email protected]> wrote: > That's a good point. The widget sizing modes are only really > documented here: > > http://excess.org/urwid/docs/manual/widgets.html#box-flow-and-fixed-widgets
Oh yes, I've been using that. That's been very helpful. But some are multicolored and I'm not sure what that means. I'd also like to add hyperlinks in the graphic to the class' reference documentation. ;-) The new docs are looking really good, overall. This is a recent change. > There isn't an unregister_signal function. Do you mean > "disconnect_signal"? Yes, that's what I meant. I'm using them quite a bit, and have even defined my own signals in some custom widgets. In the process of doing this a few general widgets (such as a pull-down-like selector) that might be of general interest. > connect_signal() does keep normal references to the function and data > that will be called, so they won't get garbage collected and you might > have to worry about leaking memory if you are regularly connecting new > functions to a long-lived widget. This behaviour allows closures to > be used as callbacks. There is some work around registering callbacks > and data with weak references that I'll be looking at merging very > soon that might be interesting to you. Ok, so I do have to explicitly disconnect signals for now. -- -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Keith Dart <[email protected]> public key: ID: 19017044 <http://www.dartworks.biz/> ===================================================================== _______________________________________________ Urwid mailing list [email protected] http://lists.excess.org/mailman/listinfo/urwid
