Hi Jesper, thanks for this episode. Indeed I already met through some code and documentation these several ways of writing calls to QObject::Connect(), but without having any idea why they all co-existed and which one was the best one. Now this is clear! Thanks for this. Cheers
Hi! I ve been following your vides of Qt/QML series since the very beginning ( amazing)! However, now since we are transitioning to a "connecting C++ and QML" section, I see that we are dealing now with Qt Widgets, which I am not familiar with at all :) My whole introduction with Qt started with your video series of Qt Quick QML and surely I did realize that in Qt there are two branches: Qt Widgets and Qt Quick QML. The question is do I need to get some Qt Widgets foundation knowledge in order to proceed with this series or I will be able to pick up? Thank you!
Hi, thanks for watching the tutorial! Indeed, there are some code examples using Qt Widgets in this and some of the coming chapters, but the course doesn't require you to know Qt Widgets to be able to follow along.
How you can call state changing method on const QObject* receiver? IMHO that is what slot expected to do change its state, and that is what it is doing in you previous example: setting some m_... variable. Or you have other overloads for 'connect' too? Then when this const/non-const is resolved: on connection or on emit?
Hi Sergiy! Thank you for your question. The const in the connect() method signature does not matter. It is casted away internally in connect(). This is so that the overload works in all cases, const and non-const objects. As long as the slot itself isn't a const method, it will be able to make changes to member variables. All the best, KDAB
Hi Jesper,
thanks for this episode. Indeed I already met through some code and documentation these several ways of writing calls to QObject::Connect(), but without having any idea why they all co-existed and which one was the best one. Now this is clear! Thanks for this.
Cheers
Hi! I ve been following your vides of Qt/QML series since the very beginning ( amazing)!
However, now since we are transitioning to a "connecting C++ and QML" section, I see that we are dealing now with Qt Widgets, which I am not familiar with at all :) My whole introduction with Qt started with your video series of Qt Quick QML and surely I did realize that in Qt there are two branches: Qt Widgets and Qt Quick QML.
The question is do I need to get some Qt Widgets foundation knowledge in order to proceed with this series or I will be able to pick up? Thank you!
Hi, thanks for watching the tutorial! Indeed, there are some code examples using Qt Widgets in this and some of the coming chapters, but the course doesn't require you to know Qt Widgets to be able to follow along.
@@KDABtv Thank you!!!
How you can call state changing method on const QObject* receiver? IMHO that is what slot expected to do change its state, and that is what it is doing in you previous example: setting some m_... variable. Or you have other overloads for 'connect' too? Then when this const/non-const is resolved: on connection or on emit?
Hi Sergiy! Thank you for your question. The const in the connect() method signature does not matter. It is casted away internally in connect(). This is so that the overload works in all cases, const and non-const objects. As long as the slot itself isn't a const method, it will be able to make changes to member variables.
All the best,
KDAB
2024