# Signals API Overview

## Abstract:

Signals and slots make up a powerful component programming mechanism.

### Signals and Slots

Signals and slots are used for communication between objects. In GUI programming we often want a change in one component to be notified to another component. More generally, we want objects of any kind to be able to communicate with one another. In ClanLib we started using signals in ClanGUI, but broadened it up into other areas, like network and input.

Older toolkits achieve this kind of communication using callbacks. A callback is a pointer to a function, so if you want a processing function to notify you about some event you pass a pointer to another function (the callback) to the processing function. The processing function then calls the callback when appropriate. Callbacks have two fundamental flaws. Firstly they are not type safe. We can never be certain that the processing function will call the callback with the correct arguments. Secondly the callback is strongly coupled to the processing function since the processing function must know which callback to call.

In ClanLib we have an alternative to the callback technique. We use signals and slots. A signal is emitted when a particular event occurs. ClanLib's components have many pre-defined signals. To handle the signals that you are interested in, you connect the signal to a slot.

Signals are emitted by objects when they change their state in a way that may be interesting to the outside world. This is all the object does to communicate. It does not know or care whether anything is receiving the signals it emits. This is true information encapsulation. A signal can be connected to as many slots as you desire.

A list box, for example, emits both highlighted() and activated() signals. Most objects will probably only be interested in activated() but some may want to know about which item in the list box is currently highlighted. If the signal is interesting to two different objects you just connect the signal to slots in both objects.

When a signal is emitted, the slots connected to it are executed immediately, just like a normal function call. The emit will return when all slots have returned.

Slots can be used for receiving signals, but they are normal member functions. A slot does not know if it has any signals connected to it.

Slot objects maintains connection state to the signals to which they are connected. When a slot object is destroyed, the signals to which it was connected will be automatically informed, and subsequently disconnected. However, this also means that it's important to be aware that you have to store the slots somewhere (even though they slots themselves are never used actively).

A minimal C++ class declaration might read:

class Foo { public: Foo(); int get_value() const { return val; } void set_value(int);

private: int val; };

Adding a signal to this:

class Foo { public: Foo(); int get_value() const { return val; } void set_value(int);

CL_Signal_v1<int> sig_value_changed;

private: int val; };

This class has the same internal state, and public methods to access the state, but in addition it has support for component programming using signals and slots: this class can tell the outside world that its state has changed by emitting a signal, sig_value_changed.

The template-type of the signal class is called CL_Signal_v1. The _v1 means void, 1 parameter. If we wanted a type with 2 parameters, we would create a signal of type CL_Signal_v2:

CL_Signal_v2<int, const std::string &text> sig_another_example; CL_Signal_v3<char, char, int> sig_yet_another_example;

Currently void is the only return type supported, so all signals are called CL_Signal_v?.

### Emitting signals

Here is a possible implementation of Foo::set_value():

void Foo::set_value(int v) { if (v != val) { val = v; sig_value_changed(v); } }

The line sig_value_changed(v) emits the signal sig_value_changed from the object. As you can see, you emit a signal by calling the signal as a function(arguments). Examples on the _v2 and _v3 signals mentioned above:

sig_another_example(10, "Hello world"); sig_yet_another_example('a', 'b', 10);

### Connecting to signals

Connecting to a signal is pretty straightforward as well:

class FooTester { public: FooTester(); void test();

private: void on_value_changed(int val);

Foo foo; CL_Slot slot_value_changed; }

FooTester::FooTester() { slot_value_changed = foo.sig_value_changed.connect(this, &FooTester::on_value_changed); }

void FooTester::test() { foo.set_value(49); }

void FooTester::on_value_changed(int val) { std::cout << "New value from foo object is " << val << std::endl; }

Explanation:

CL_Slot slot_value_changed;

Make sure you store the CL_Slot object somewhere, otherwise the slot is disconnected when it is destroyed (goes out of scope for instance). Put it in your class definition or similar; just don't make it a local variable.

slot_value_changed = foo.sig_value_changed.connect(this, &FooTester::on_value_changed);

Each signal has a connect() function, which returns a CL_Slot object you need to keep. It takes two parameters; the object of the receiving slot, and the definition of the receiving slot. Most often the first argument will be this, but you can actually connect it to another class than your current object:

slot_value_changed = foo.sig_value_changed.connect(myOtherObject, &OtherObject::on_value_changed);

### Slot Container

CL_SlotContainer is a utility class which can store CL_Slots for you. Its syntax is as follows: `CL_SlotContainer slots; ... slots.connect(mySignal1, this, &MyApp::on_signal1); slots.connect(mySignal2, this, &MyApp::on_signal2); slots.connect(mySignal3, this, &MyApp::on_signal3);`

You see the syntax for connecting signals using a CL_SlotContainer is a little bit different than the CL_Slot method (example below).

`CL_Slot slot1, slot2, slot3; ... slot1 = mySignal1.connect(this, &MyApp::on_signal1); slot2 = mySignal2.connect(this, &MyApp::on_signal2); slot3 = mySignal3.connect(this, &MyApp::on_signal3);`

### Specific ClanLib signals

All signals in ClanLib is a little bit different than explained in this overview so far - they are all functions. The only effect this has on your code is that you put parenthesis behind the signal when connecting to it. Some examples:

`CL_Mouse: (clanDisplay) static CL_Signal_v2<int, int> &sig_move(); static CL_Signal_v1<const CL_Key &> &sig_button_press(); static CL_Signal_v1<const CL_Key &> &sig_button_release(); CL_Component: (clanGUI) CL_Signal_v1<const CL_Key &> & sig_mouse_down(); CL_Button: (clanGUI) CL_Signal_v1<bool> &sig_toggled(); CL_Signal_v0 &sig_clicked(); Usage examples: CL_Slot slot1 = CL_Mouse::sig_move().connect(this, &App::on_mouse_move); CL_Slot slot2 = button->sig_clicked().connect(this, &GUIApp::on_button_clicked); CL_Slot slot3 = component->sig_mouse_down().connect(this, &GUIApp::on_component_mouse_down); void App::on_mouse_move(int x, int y); void GUIApp::on_button_toggled(bool state); void GUIApp::on_component_mouse_down(const CL_Key &key);`

As you see, the only different is the parenthesis - sig_clicked() instead of sig_clicked.

### More examples

If you need to see some real world examples of signals and slots, have a look at the GUI overview.

Thanks to TrollTech and their QT toolkit for their Signal & Slot explanation; this overview was based on theirs.