This might sound somewhat uninteresting at first, but it means you can have your own signals and slots outside the main thread. The Trolls created a new way to connect signals to slots such that signals can actually cross thread boundaries. I can now emit a signal in one thread and receive it in a slot in a different thread. Signals and slots are loosely coupled: A class which emits a signal neither knows nor cares which slots receive the signal. Qt's signals and slots mechanism ensures that if you connect a signal to a slot, the slot will be called with the signal's parameters at the right time. Signals and slots can take any number of arguments of any type.

Signals are a neat feature of Qt that allow you to pass messages between different components in your applications.

Signals are connected to slots which are functions (or methods) which will be run every time the signal fires. Many signals also transmit data, providing information about the state change or widget that fired them. The receiving slot can use this data to perform different actions in response to the same signal.

However, there is a limitation: the signal can only emit the data it was designed to. So for example, a QAction has a .triggered that fires when that particular action has been activated. The triggered signal emits a single piece of data -- the checked state of the action after being triggered.

1. The connection mechanism uses a vector indexed by signals. But all the slots waste space in the vector and there are usually more slots than signals in an object. So from Qt 4.6, a new internal signal index which only includes the signal index is used. While developing with Qt, you only need to know about the absolute method index.
2. There is no such slot - 'display(5)'. (But there is 'display(int)')Parameters to slots are automatically passed from signals. As there is no 'clicked(int)', it would be best for you to create a new class derived from QLCDNumber and create a new slot in it.
3. Connecting in Qt 5. There are several ways to connect a signal in Qt 5. Qt 5 continues to support the old string-based syntax for connecting signals and slots defined in a QObject or any class that inherits from QObject (including QWidget).

For non-checkable actions, this value will always be False

The receiving function does not know whichQAction triggered it, or receiving any other data about it.

This is usually fine. You can tie a particular action to a unique function which does precisely what that action requires. Sometimes however you need the slot function to know more than that QAction is giving it. This could be the object the signal was triggered on, or some other associated metadata which your slot needs to perform the intended result of the signal.

This is a powerful way to extend or modify the built-in signals provided by Qt.

Intercepting the signal

Instead of connecting signal directly to the target function, youinstead use an intermediate function to intercept the signal, modify the signal data and forward that on to your actual slot function.

This slot function must accept the value sent by the signal (here the checked state) and then call the real slot, passing any additional data with the arguments.

Rather than defining this intermediate function, you can also achieve the same thing using a lambda function. As above, this accepts a single parameter checked and then calls the real slot.

In both examples the <additional args> can be replaced with anything you want to forward to your slot. In the example below we're forwarding the QAction object action to the receiving slot.

Our handle_trigger slot method will receive both the original checked value and the QAction object. Or receiving slot can look something like this

Below are a few examples using this approach to modify the data sent with the MainWindow.windowTitleChanged signal.

• PyQt5
• PySide2

The .setWindowTitle call at the end of the __init__ block changes the window title and triggers the .windowTitleChanged signal, which emits the new window title as a str. We've attached a series of intermediate slot functions (as lambda functions) which modify this signal and then call our custom slots with different parameters.

Running this produces the following output.

The intermediate functions can be as simple or as complicated as you like -- as well as discarding/adding parameters, you can also perform lookups to modify signals to different values.

In the following example a checkbox signal Qt.Checked or Qt.Unchecked is modified by an intermediate slot into a bool value.

• PyQt5
• PySide2

In this example we've connected the .stateChange signal to result in two ways -- a) with a intermediate function which calls the .result method with True or False depending on the signal parameter, and b) with a dictionary lookup within an intermediate lambda.

Running this code will output True or False to the command line each time the state is changed (once for each time we connect to the signal).

QCheckbox triggering 2 slots, with modified signal data

Trouble with loops

One of the most common reasons for wanting to connect signals in this way is when you're building a series of objects and connecting signals programmatically in a loop. Unfortunately then things aren't always so simple.

If you try and construct intercepted signals while looping over a variable, and want to pass the loop variable to the receiving slot, you'll hit a problem. For example, in the following code we create a series of buttons, and use a intermediate function to pass the buttons value (0-9) with the pressed signal.

• PyQt5
• PySide2

Qt Execute Slot Without Signal Booster

If you run this you'll see the problem -- no matter which button you click on you get the same number (9) shown on the label. Why 9? It's the last value of the loop.

The problem is the line lambda: self.button_pressed(a) where we pass a to the final button_pressed slot. In this context, a is bound to the loop.

We are not passing the value of a when the button is created, but whatever value a has when the signal fires. Since the signal fires after the loop is completed -- we interact with the UI after it is created -- the value of a for every signal is the final value that a had in the loop: 9.

Qt Execute Slot Without Signal Number

So clicking any of them will send 9 to button_pressed

The solution is to pass the value in as a (re-)named parameter. This binds the parameter to the value of a at that point in the loop, creating a new, un-connected variable. The loop continues, but the bound variable is not altered.

This ensures the correct value whenever it is called.

You don't have to rename the variable, you could also choose to use the same name for the bound value.

The important thing is to use named parameters. Putting this into a loop, it would look like this:

Running this now, you will see the expected behavior -- with the label updating to a number matching the button which is pressed.

The working code is as follows:

Qt Execute Slot Without Signal Generator

• PyQt5
• PySide2