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.
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.