View source for How to Use Signals and Slots

[[Category:HowTo]]
[[Category:Snippets]]
[[Category:Tutorial]]
[[Category:Learning]]

__NOEDITSECTION__
<div style="float:left;padding:14px;">__TOC__</div>

== Introduction ==

Remember old X-Windows ''call-back'' system? Generally it isn't type safe and flexible. There are many problems with them. Qt offers a new event handling system: ''signal-slot'' connections. Imagine an alarm clock. When alarm is ringing, a signal is being sent (''emit''). And you're handling it in a slot.

* Every QObject class may have as many signals and slots as you want
* You can emit signals only from within that class, where the signal is located
* You can ''connect'' signal with another signal (make chains of signals);
* Every signal and slot can have unlimited count of connections with other.
* '''ATTENTION!''' You can't set default value in slot attributes e.g. <tt>void mySlot(int i = 0);</tt>

== Connection ==

You can connect signal with this template:

<code>
QObject::connect (
  const QObject * sender,
  const char * signal,
  const QObject * receiver,
  const char * method
);
</code>

You have to wrap <tt>const char * signal</tt> and <tt>const char * method</tt> into SIGNAL() and SLOT() macros.

And you also can disconnect signal-slot:

<code>
QObject::disconnect (
  const QObject * sender,
  const char * signal,
  const QObject * receiver,
  const char * method
);
</code>

== Deeper ==

Widgets emit signals when events occur. For example, a button will emit a ''clicked'' signal when it is clicked. A developer can choose to connect to a signal by creating a function (a ''slot'') and calling the <tt>connect()</tt> function to relate the signal to the slot. Qt's signals and slots mechanism does not require classes to have knowledge of each other, which makes it much easier to develop highly reusable classes. Since signals and slots are type-safe, type errors are reported as warnings and do not cause crashes to occur.

For example, if a Quit button's <tt>clicked()</tt> signal is connected to the application's <tt>quit()</tt> slot, a user's click on Quit makes the application terminate. In code, this is written as

<code>
connect(button, SIGNAL (clicked()), qApp, SLOT (quit()));
</code>

Connections can be added or removed at any time during the execution of a Qt application, they can be set up so that they are executed when a signal is emitted or queued for later execution, and they can be made between objects in different threads.

The signals and slots mechanism is implemented in standard C++. The implementation uses the C++ preprocessor and <tt>moc</tt>, the [http://doc.qt.io/qt-5/moc.html Meta Object Compiler], included with Qt. Code generation is performed automatically by Qt's build system. Developers never have to edit or even look at the generated code.

In addition to handling signals and slots, the Meta Object Compiler supports Qt's translation mechanism, its property system, and its extended runtime type information. It also makes runtime introspection of C++ programs possible in a way that works on all supported platforms.

To make moc compile the meta object classes don't forget to add the <tt>Q_OBJECT</tt> macro to your class.