Signal editor (was Re: [Glade-devel] small patch)

[bighead@users.sourceforge.net]

Hey

I kinda agree, showing all signals ain't really a good thing. For Example
GtkButton has IIRC 4-5 signals, but which one is used most? clicked, ofcourse!
Also know one ever uses signals for GtkButton's parents (not that I know of).

Probably a way where you can select the parent class in menu containing the 
heirarchy, which then shows all signals from that parent class to the present
class.

Archit

Tommi Komulainen <tommi.komulainen@nokia.com> writes:

> On Tue, 2004-01-13 at 23:11, ext Joaquin Cuenca Abela wrote:
> > Hi!
> > 
> > I've been hacking a bit on the signal editor.
> > 
> > What do you think of an interface like that one:
> > 
> > http://e98cuenc.free.fr/signals.png
> 
> Hmm.. that feels unnecessarily crowded to my taste.  It's showing all
> possible signals for every widgets, and yet you usually only ever use
> one or two.  Keeping signals like 'map' always visible makes the dialog
> pretty cluttered.  IMHO, it would make more sense to show only those
> signals for which you have added a handler.
> 
> I'm all for editing the signals in place, direct manipulation is nicer
> (and simpler since you don't need a separate entry just for editing)
> 
> 
> Can anyone make an educated guess whether or not the ability to add
> multiple handlers for the same signal is actually used in practice? 
> It's obviously making the UI more complicated, but is the feature useful
> enough to warrant that, I don't really know...
> 
> 
> -- 
> Tommi Komulainen <tommi.komulainen@nokia.com>
> _______________________________________________
> Glade-devel maillist  -  Glade-devel@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/glade-devel