Re: Generic way to identify emitted signals

[Murray Cumming <murrayc murrayc com>]

On Wed, 2004-11-03 at 13:54 +0100, Dirk Neumann wrote:
> Hi all,
> 
> is there a generic way to identify an emitted signal? For example, if a Gtk::Button is clicked, a signal_clicked is emitted. I know this, and so I can connect a signal-handler via something like mybottun->signal_clicked().connect(...). Fine. But what to do, if I don't know which signal is emitted? Do I have to use the try-and-error-method to find that out?
> This is a simple example, but I don't find the correct signal, when I have a Gtk::TreeView widget and I put a cursor into an editable cell. There are many suitable signals from Gtk::Widget, Gtk::TreeModel and so on.

Good news:
gtkmm 2.4 has less signals than gtkmm 2.2, so you don't need to be
confused by the extra signals that you should never use.

Bad news:
Signals are one part of GTK+ and gtkmm that is currently not well
documented. I think that each signal should have some information about
exactly when it will be emitted. New GTK+ 2.4 signals do tend to have
more documentation, though we don't reuse that documentation in gtkmm
yet.

This does need someone to make an effort to go through the widgets and
document the signals in GTK+. If you (or someone) has time for that,
then you should ask about it on gtk-list gnome org 
 
-- 
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com