The SignalProxy provides an API similar to sigc::signal that can be used to connect sigc::slots to glib signals. More...
The SignalProxy provides an API similar to sigc::signal that can be used to connect sigc::slots to glib signals.
This holds the name of the glib signal and the object which might emit it. Actually, proxies are controlled by the template derivatives, which serve as gatekeepers for the types allowed on a particular signal.
sigc::slot_base& Glib::SignalProxyNormal::connect_ |
( |
const sigc::slot_base & |
slot, |
|
|
bool |
after |
|
) |
| |
|
protected |
Connects a signal to a generic signal handler.
This is called by connect() in derived SignalProxy classes.
@param slot The signal handler, usually created with sigc::mem_fun(), or sigc::ptr_fun().
@param after Whether this signal handler should be called before or after the default signal handler.
sigc::slot_base& Glib::SignalProxyNormal::connect_notify_ |
( |
const sigc::slot_base & |
slot, |
|
|
bool |
after |
|
) |
| |
|
protected |
Connects a signal to a signal handler without a return value.
This is called by connect() in derived SignalProxy classes.
By default, the signal handler will be called before the default signal handler, in which case any return value would be replaced anyway by that of the later signal handler.
- Parameters:
-
slot | The signal handler, which should have a void return type, usually created with sigc::mem_fun(), or sigc::ptr_fun(). |
after | Whether this signal handler should be called before or after the default signal handler. |