Skip to main content

QT - Signal-slot mechanism

This is first article describing some aspects of programming with Qt framework. I am going to focus on most important basic feature of Qt framework: signal-slot mechanism.

At the beginning take a look on below QT code:

Output of that code is this window:


This quick code is something like "Hello world" of Qt programming. Let's take a detailed look on the code.

In point I we are declaring QApplication object which will contain indefinite loop which will be invoked after program starts in order to wait for user interactions. We can also analyse command line input parameters in this line, but we are not doing it because we do not have any input parameters for our application.

In point II we are declaring QPushButton object which will be the only object of our application. As only parameter of our definition we are putting text which should be displayed on our button - "Hello World".

Point III is key point of this example. It presents basic usage of signal-slot mechanism. We are using QObject::connect function here to bind signal and slot.
This function has following syntax:
QObject::connect(senderObject, SIGNAL(senderSignal), receiverObject, SLOT(receiverSlot))

Where:
  • senderObject - object where signal is send from
  • SIGNAL(senderSignal) - signal which is send to receiverObject
  • receiverObject - object will should receiver sent signal
  • SLOT(receiverSlot) - slot function which should be invoked after receiving signal in receiverObject
In our case we are connecting signal clicked() from our button object with function quit() of our application. Signal clicked() is emitted when user clicks on button object. It means that when user clicks on button object signal clicked() will be captured by receiverObject. Then receiverObject runs function quit(). Than function closes our application.

Basic idea of QT signal-slot mechanism is invoking some function of one QT object by sending signal from another QT object.

In point IV we are invoking function show() of our QPushButton which displays our button on screen.

In point V we are starting our application. Function exec() contains infinite loop which will listen for user interactions.

As usual, code of this example you can find on our github account: Signal-Slot mechanism
Labels:

Comments

  1. Anonymous5 December 2013 at 21:24

    very good and quick explanation - more QT articles, please

    ReplyDelete

Post a Comment

Popular posts from this blog

Advanced C++ - Mutable Class Field

Today I would like to present C++ class' feature called mutable class field . Mutable class field is class' field modifier which allows to change its value even if object of the class is declared as const . Take a look at the example: Output of this example is: In point I of that example we are defining object of TestClass . Note that this object is const . As you can see in point Ia this class has three different member fields ( constInt, mutableConstInt, nonConstInt ). Those variables are public for this example, but do not worry about encapsulation here. It is just omitted for simplify this example. As you can see one of this member fields is marked as mutable class file using mutable keyword ( mutableConstInt ). Such variable can be modified even if object of class TestClass is const . It will be explained in next points of this example. In point II we are printing default values of testObject object initialized in initialization list of TestClass' default c...
Post a Comment
Read more

C++ Multithreading - Race conditions

In the previous C++ Multithreading article I presented you how to pass parameters between threads. Take a detail look on the output of that example once again: In the first line of that output you can notice that output text from two threads is mixed. You are probably wondering why it happens? It is because we are not protecting resources which are shared by two threads (in this example cout stream is shared in both threads) which causes multithreading's phenomenon called race condition . Because threads switching and accessing to shared resources are managed by operating system we do not know when std::cout stream will be accessed by main thread and when it will be accessed by second thread. Therefore in the previous article I mentioned that output of the example can be little different on your computer than my output example. What's more it is possible that this output will be different for few consecutive invoking of the example on the same machine. It is beca...
Post a Comment
Read more

C++14 - Tuple addressing via type

Today I would like to introduce one of new features which will arrive to C++ with new language standard (C++14) which is going to be release in 2014. In order to compile example from this article you need to have compiler supporting C++14 standard. The newest version of GCC supports it. I would like to introduce you features called Tuple addressing via type which allows us to get tuple element value using type name instead of tuple parameter number. Of course it is possible only for type names which are not ambiguous. Let's take a look on below example for better understanding: In point I we are declaring our tuple type containng of 2 int elements and on string element. In point II we are using std::get function to get values of our tuple typed variable using tuple parameters numbers. This feature is well known from C++11 standard. Point III shows new (introduced in C++14 standard) way of getting values of tuple elements. We are getting string type element using...
Post a Comment
Read more