Active Topics
-
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 1 day, 7 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 2 days, 3 hrs ago - more...
|
2013-12-04
, 20:10
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#12
|
Originally Posted by xerxes2
The app is single threaded - everything happens in the main event loop. Everything (signals, slots, timers, networking) is frozen during aboutToQuit() call. That's why i'd need a second event loop to do processing without exiting aboutToQuit() in main thread.
Why are you calling eventLoop.exec()? You already has one mainloop running so just put your cleanup code in the aboutToQuit callback instead. The mainloop will not exit before the aboutToQuit callback returns. There was a bug in earlier sdk but in the latest version it works just fine.
|
|
2013-12-04
, 20:13
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#13
|
Originally Posted by coderus
..to which event in which object? As i wrote in the original post, i already tried it with no success.
install event filter
 |
|
2013-12-04
, 20:26
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#14
|
Originally Posted by vranki
Afaik you can only have one mainloop in both gtk and qt. I've never heard anything about having two.
The app is single threaded - everything happens in the main event loop. Everything (signals, slots, timers, networking) is frozen during aboutToQuit() call. That's why i'd need a second event loop to do processing without exiting aboutToQuit() in main thread.
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
|
|
2013-12-04
, 20:35
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#15
|
I think the reason for newly started main loop is in qwaylandeventthread.cpp line 37:
https://qt.gitorious.org/qt/qtwaylan...thread.cpp#L37
When app window is closed, the Wayland connection is broken and if something (in the new mainloop?) calls readWaylandEvents(), the process is killed.
https://qt.gitorious.org/qt/qtwaylan...thread.cpp#L37
When app window is closed, the Wayland connection is broken and if something (in the new mainloop?) calls readWaylandEvents(), the process is killed.
 |
|
2013-12-04
, 20:59
|
|
Posts: 6,436 |
Thanked: 12,699 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#16
|
okay, event filtering seems not to work in emulator, try:
and why not to use main class destructor for this purpose?
and
Code:
app->connect( app, SIGNAL(lastWindowClosed()), app, SLOT(quit()) ); app->connect( app, SIGNAL(aboutToQuit()), app, SLOT(quit()) );
and
Code:
int retVal = app->exec();
qDebug() << "App exiting with code:" << QString::number(retVal);
//you can do whatever here
return retVal;
|
|
2013-12-04
, 21:28
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#17
|
Originally Posted by coderus
Signals, slots, networking, and all other asynchronous stuff does not work without a event loop. And i need those.
and why not to use main class destructor for this purpose?
Code://you can do whatever here
|
|
2013-12-04
, 21:32
|
|
Posts: 6,436 |
Thanked: 12,699 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#18
|
what about other methods?
|
|
2013-12-05
, 00:04
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#19
|
Originally Posted by vranki
Well thats surprising - I've been using setQuitOnLastWindowClosed in Maemo, Harmattan, Windows and desktop Linux at least for the last two years in qgvdial to achieve exactly what you need: Running the application in the background.
Does not work - the main loop still exits. Same with Harmattan.
https://code.google.com/p/qgvdial/so...k/src/main.cpp
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.
If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.
If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
|
|
2013-12-05
, 12:19
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#20
|
Originally Posted by uvatbc
Ok, i think i'll need to create a simple test application for this issue.
Well thats surprising - I've been using setQuitOnLastWindowClosed in Maemo, Harmattan, Windows and desktop Linux at least for the last two years in qgvdial to achieve exactly what you need: Running the application in the background.
https://code.google.com/p/qgvdial/so...k/src/main.cpp
Telegram | Openrepos | GitHub | Revolut donations