On Mon, Jul 26, 2004 at 02:40:54PM -0500, Skip Montanaro wrote: > I discovered that some widgets only emit signals when values are > changed via keyboard action, not mouse action. For instance, the > paned widget only emits a move-handle signal when the separator is > moved using a handful of keys (page up, etc). It's not emitted when > the separator is dragged with the mouse. It's not at all obvious to > me why the signal should be emitted in one case but not the other. I > think the SpinButton has a similar trait.
It *really* looks like a bug to me, but I'm surprised the SpinButton would have the same issue. Are you sure this is reproducible using a simple testcase? Are you using the appropriate signal, or is there some other one that makes itself more useful in this situation? If nothing seems to make sense, let's file a bug --- let Owen figure out a way to `RESO NOTABUG' it <wink>. Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
