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

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

Advanced C++ - Stack unwinding

Stack unwinding is normally a concept of removing function entries from call stack (also known as Execution stack, Control stack, Function stack or Run-time stack). Call Stack is a stack data structure that stores active functions' addresses and helps in supporting function call/return mechanism. Every time when a function is called, an entry is made into Call stack which contains the return address of the calling function where the control needs to return after the execution of called function. This entry is called by various names like stack frame , activation frame or activation record. With respect to exception handling , stack Unwinding is a process of linearly searching function call stack to reach exception handler. When an exception occurs, if it is not handled in current function where it is thrown, the function Call Stack is unwound until the control reaches try block and then passes to catch block at the end of try block to handle exception. Also, in this proc...
Post a Comment
Read more

Advanced C++ - Template Functions

Template function are special types of C++ function which can be used with different types (generic types). Thanks to that we can create one body of function which can be used for many different types. When we are creating template function compiler does not define any function for use at that time. Generation of funciton basing on templates are done during compilation process basing of differnt usage of template class. For better understanding take a look on following example: Output of this example is: In point I, we are defining template function which should return sum of two parameters. Without templates we need to define such function separately for each type which we should use it with (ex. separate function for int type, separate for double , separate for any other type). Thanks to template we can generate body of that function only once (as in point I) and use it to any type which is able to use body of that function. In our example we can use this template for an...
Post a Comment
Read more