I can imagine that there might be quite a few of them depending on the event, but at the same time, I guess this can be a best way to debug, and an interesting lesson.
Why would I need it? I'm using some custom class based on the QWidget
, which does not expand when I de-attach a QDockWidget
based in the same window. Knowing what signals are emitted when this dock widget is being de-attached would help me to chose which method I need to overwrite in my custom class.
In other words, I don't want to check every possible signal from the documentation, but just see which signals are emitted when I perform some action in my application.
If you're using PyQT5 instead of Qt5, you can use Python's introspection abilities to find all signals of any class and connect them to a dummy slot (of a dummy object).
#!/usr/bin/env python
# -*- coding: utf-8 -*-
from typing import Iterable
from PyQt5.QtCore import pyqtBoundSignal
from PyQt5.QtCore import pyqtSlot
from PyQt5.QtCore import QObject
def list_all_signals(obj: QObject) -> Iterable[pyqtBoundSignal]:
attr_names = dir(obj)
attributes = (getattr(obj, attr_name) for attr_name in attr_names)
connectable = filter(lambda l: hasattr(l, "connect"), attributes)
return connectable
class SignalListener(QObject):
@pyqtSlot()
def universal_slot(self, *args, **kwargs):
print("Signal caught" + 30 * "-")
print("sender:", self.sender())
meta_method = (
self.sender().metaObject().method(self.senderSignalIndex())
)
print("signal:", meta_method.name())
print("signal signature:", meta_method.methodSignature())
SIGNAL_LISTENER = SignalListener()
def spy_on_all_signals(
obj: QObject, listener: SignalListener = SIGNAL_LISTENER
):
for signal in list_all_signals(obj):
signal.connect(SIGNAL_LISTENER.universal_slot)
The dummy slot now prints info about all signals emitted by an object. For example, if you spy on a random QLineEdit like this:
some_line_edit = QLineEdit(self)
spy_on all_signals(some_line_edit)
A possible log of entering and exiting the line edit might look like this:
Signal caught ------------------------------
sender: <PyQt5.QtWidgets.QLineEdit object at 0x7f220f7a3370>
signal: b'cursorPositionChanged'
signal signature: b'cursorPositionChanged(int,int)'
Signal caught ------------------------------
sender: <PyQt5.QtWidgets.QLineEdit object at 0x7f220f7a3370>
signal: b'selectionChanged'
signal signature: b'selectionChanged()'
Signal caught ------------------------------
sender: <PyQt5.QtWidgets.QLineEdit object at 0x7f220f7a3370>
signal: b'selectionChanged'
signal signature: b'selectionChanged()'
Signal caught ------------------------------
sender: <PyQt5.QtWidgets.QLineEdit object at 0x7f220f7a3370>
signal: b'editingFinished'
signal signature: b'editingFinished()'
You may want to take a look at the QSignalSpy class. I think though you have to connect manually the signal you want to spy.
This isn't possible with any public API.
But, if you put your code into a QTestLib-based unit test, you can run the unit test with -vs
to print out every emitted signal.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With