I have some time working with Qt and I have always used private slots. I have never thought too much about it.
QTestLib API. All public methods are in the QTest namespace. In addition, the QSignalSpy class provides easy introspection for Qt's signals and slots. Using QTestLib Creating a Test. To create a test, subclass QObject and add one or more private slots to it. Each private slot is a testfunction in your test. Jun 06, 2011 Thanks for the advice, but now I have another question. Even without the signals and slots, I tried to make it so that it did qDebug. Thanks for the advice, but now I have another question. Even without the signals and slots, I tried to make it so that it did qDebug.
Currently, I have an application with several dialog boxes, which in turn have a number of widgets. The functionalities that must be executed when the user interacts with such widgets
are implemented as slots. Example: Clicking on a particular button zooms in on an image that is displayed.
Now I ask myself:
Signal And Slot In Qt
Is it correct that such slots are private?
Would it be of any use to make such public slots?
What is expected (standard) in these cases?