Closing program when widget is closed.

[metdos]

Thanks for the "qApp" tip.

and sorry for the bad names I gave to functions. Actually there is no other thread, there is just a function with infinite loop and I added "a->processEvents();" in order to prevent freezing in widgets as you can see in code above.

Simply ReceiveThread() continues to run infinite loop when widget is closed, I need to stop this infinite loop.

Thanks anyway

[wagmare]

in rovkonInterface class
is it a QDialog or QWidget ..
if QDialog we can receive
void QDialog::rejected ()
with that rejected call we can quit our application like

QObject::connect( w, SIGNAL(rejected()), qApp, SLOT(quit()) );

QObject::connect( w, SIGNAL(rejected()), qApp, SLOT(quit()) );

To copy to clipboard, switch view to plain text mode 

[metdos]

It is Qwidget.

rovkonInterface w; //subclass of Qwidget

rovkonInterface w; //subclass of Qwidget

To copy to clipboard, switch view to plain text mode 

in rovkonInterface class
is it a QDialog or QWidget ..
if QDialog we can receive
void QDialog::rejected ()
with that rejected call we can quit our application like

QObject::connect( w, SIGNAL(rejected()), qApp, SLOT(quit()) );

QObject::connect( w, SIGNAL(rejected()), qApp, SLOT(quit()) );

To copy to clipboard, switch view to plain text mode 

[wagmare]

so u try emit your custom signal on rovkonInterface closeEvent()

reimplement closeEvent() in rovkonInterface() class
emit widgetClosed() // your custom signal
and

QObject::connect( w, SIGNAL(widgetClosed()), qApp, SLOT(quit()) );

[spirit]

so u try emit your custom signal on rovkonInterface closeEvent()

reimplement closeEvent() in rovkonInterface() class
emit widgetClosed() // your custom signal
and

QObject::connect( w, SIGNAL(widgetClosed()), qApp, SLOT(quit()) );

in that case you don't need to emit a signal, just call qApp->quit(); in closeEvent.

[metdos]

didn't work,

Even I don't understand how closing QT application will terminate main program.

As long as I understand, I using an instance of QT class, and when user closed the widget, this instance will gone, but how it can effect my other function with infinite loop. So if I can find a way which inform me that instance of Qt class is closed, I think that I can solve my problem.

[spirit]

there is such signal QObject::destroyed.

[wagmare]

didn't work,

Even I don't understand how closing QT application will terminate main program.

As long as I understand, I using an instance of QT class, and when user closed the widget, this instance will gone, but how it can effect my other function with infinite loop. So if I can find a way which inform me that instance of Qt class is closed, I think that I can solve my problem.

see every Qt application will have QApplication

from docs:

For any GUI application that uses Qt, there is precisely one QApplication object, no matter whether the application has 0, 1, 2 or more windows at any time.

so qApp->quit() will try to close that QApplication .. Tells the application to exit with return code 0 (success).

[numbat]

QCoreApplication::quit or QCoreApplication::exit simply stop event processing, so that a call to QCoreApplication::exec will return. In your app, you never get to exec because you are in an infinite loop. You are on the right track with your lMustQuit variable, but you never set it to true. One method would be to connect the lastWindowClosed signal to a custom function and set lMustQuit to be true. Fortunately, we can alternatively use QEventLoop which has a method QEventLoop::isRunning which tells us when exit or quit have been called. Here is a simple example:

#include <QtGui/QApplication>
#include "mainwindow.h"
#include <QEventLoop>
 
void ReceiveThread();
 
int main(int argc, char *argv[])
{
 
    //GUI part
    QApplication a(argc, argv);
    QWidget w; //subclass of Qwidget
    w.show();
 
    QObject::connect( qApp, SIGNAL(lastWindowClosed()), qApp, SLOT(quit()) );
 
    // start the receive thread
    ReceiveThread();
 
    /* We only get here after quit is called. */
    return 0;
 
}
 
void ReceiveThread()
{
    QEventLoop loop;
 
    while (loop.isRunning()) /* Returns false after exit or quit have been called. */
    {
        loop.processEvents();
    }
}

#include <QtGui/QApplication>
#include "mainwindow.h"
#include <QEventLoop>

void ReceiveThread();

int main(int argc, char *argv[])
{

    //GUI part
    QApplication a(argc, argv);
    QWidget w; //subclass of Qwidget
    w.show();

    QObject::connect( qApp, SIGNAL(lastWindowClosed()), qApp, SLOT(quit()) );

    // start the receive thread
    ReceiveThread();

    /* We only get here after quit is called. */
    return 0;

}

void ReceiveThread()
{
    QEventLoop loop;

    while (loop.isRunning()) /* Returns false after exit or quit have been called. */
    {
        loop.processEvents();
    }
}

To copy to clipboard, switch view to plain text mode 

[metdos]

Yes, these are the magical lines I'm searching.

QEventLoop loop;
loop.isRunning()

QEventLoop loop;
loop.isRunning()

To copy to clipboard, switch view to plain text mode 

and thanks, it helped very much.

QCoreApplication::quit or QCoreApplication::exit simply stop event processing, so that a call to QCoreApplication::exec will return. In your app, you never get to exec because you are in an infinite loop. You are on the right track with your lMustQuit variable, but you never set it to true. One method would be to connect the lastWindowClosed signal to a custom function and set lMustQuit to be true. Fortunately, we can alternatively use QEventLoop which has a method QEventLoop::isRunning which tells us when exit or quit have been called. Here is a simple example:

#include <QtGui/QApplication>
#include "mainwindow.h"
#include <QEventLoop>
 
void ReceiveThread();
 
int main(int argc, char *argv[])
{
 
    //GUI part
    QApplication a(argc, argv);
    QWidget w; //subclass of Qwidget
    w.show();
 
    QObject::connect( qApp, SIGNAL(lastWindowClosed()), qApp, SLOT(quit()) );
 
    // start the receive thread
    ReceiveThread();
 
    /* We only get here after quit is called. */
    return 0;
 
}
 
void ReceiveThread()
{
    QEventLoop loop;
 
    while (loop.isRunning()) /* Returns false after exit or quit have been called. */
    {
        loop.processEvents();
    }
}

#include <QtGui/QApplication>
#include "mainwindow.h"
#include <QEventLoop>

void ReceiveThread();

int main(int argc, char *argv[])
{

    //GUI part
    QApplication a(argc, argv);
    QWidget w; //subclass of Qwidget
    w.show();

    QObject::connect( qApp, SIGNAL(lastWindowClosed()), qApp, SLOT(quit()) );

    // start the receive thread
    ReceiveThread();

    /* We only get here after quit is called. */
    return 0;

}

void ReceiveThread()
{
    QEventLoop loop;

    while (loop.isRunning()) /* Returns false after exit or quit have been called. */
    {
        loop.processEvents();
    }
}

To copy to clipboard, switch view to plain text mode 

[metdos]

Again me, yes it helped to stop program, but this time program does not enter infinite loop.
loop.isRunning() is returning false every time.

Yes, these are the magical lines I'm searching.

QEventLoop loop;
loop.isRunning()

QEventLoop loop;
loop.isRunning()

To copy to clipboard, switch view to plain text mode 

and thanks, it helped very much.

[wagmare]

switch to threads ... QThread is the best option here .. no need for u to use
qApp->processEvents()

refer this documentation
http://doc.trolltech.com/qq/qq27-responsive-guis.html

[metdos]

Very good and neat article.

refer this documentation
http://doc.trolltech.com/qq/qq27-responsive-guis.html