Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 13 hrs, 32 mins ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 2 days, 10 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 3 days, 7 hrs ago - more...
 |
|
2013-12-04
, 17:15
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#2
|
It's not exactly what you're asking, but you could create a daemon and control it from your application via dbus, so you don't have to work around the close event.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jolla –– contactlaunch –– timenow
Nemo UX blog: Grog
My website: qwazix.com
My job: oob
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jolla –– contactlaunch –– timenow
Nemo UX blog: Grog
My website: qwazix.com
My job: oob
 |
|
2013-12-04
, 17:22
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#3
|
I think what you want is the aboutToQuit signal which doesn't quit the mainloop until its callback returns.
http://qt-project.org/doc/qt-5.0/qtc...ml#aboutToQuit
http://qt-project.org/doc/qt-5.0/qtc...ml#aboutToQuit
__________________
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
, 17:48
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#4
|
How about
in main.cpp?
Code:
app->setQuitOnLastWindowClosed(false);
__________________
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock
| The Following User Says Thank You to pycage For This Useful Post: | ||
 |
|
2013-12-04
, 17:48
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#5
|
Originally Posted by vranki
Actually the reason is that closing the last window generates a quit event. See http://qt-project.org/doc/qt-4.8/qap...dowClosed-prop
I'm writing an application which has to do dome network operations after user has closed the UI. Normally this is not possible, as the applications Qt main loop exits when closing the UI.
|
|
2013-12-04
, 19:36
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#6
|
Originally Posted by pycage
Does not work - the main loop still exits. Same with Harmattan.
Code:app->setQuitOnLastWindowClosed(false);
|
|
2013-12-04
, 19:47
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#7
|
Originally Posted by xerxes2
I created a aboutToQuit slot like this:
I think what you want is the aboutToQuit signal which doesn't quit the mainloop until its callback returns.
http://qt-project.org/doc/qt-5.0/qtc...ml#aboutToQuit
Code:
// Called when app about to quit - handle upsync & quitting
void ClientLogic::aboutToQuit() {
qDebug() << Q_FUNC_INFO;
QEventLoop eventLoop;
eventLoop.exec();
}
Code:
virtual void ClientLogic::aboutToQuit() The Wayland connection broke. Did the Wayland compositor die? Killing all inferiors Debugging has finished
 |
|
2013-12-04
, 19:54
|
|
Posts: 6,436 |
Thanked: 12,699 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#8
|
why you need this? isnt better to rewrite logics?
set event filter, catch close event, do whatever.
set event filter, catch close event, do whatever.
|
|
2013-12-04
, 20:00
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#9
|
Originally Posted by vranki
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.
I created a aboutToQuit slot like this:
On emulator quitting with this results in output:Code:// Called when app about to quit - handle upsync & quitting void ClientLogic::aboutToQuit() { qDebug() << Q_FUNC_INFO; QEventLoop eventLoop; eventLoop.exec(); }
Debugger just displays ??'s as stack trace so it's useless. The crash happens when eventLoop.exec() is called.Code:virtual void ClientLogic::aboutToQuit() The Wayland connection broke. Did the Wayland compositor die? Killing all inferiors Debugging has finished
http://talk.maemo.org/showthread.php...ht=abouttoquit
__________________
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!!).
Last edited by xerxes2; 2013-12-04 at 20:03.
|
|
2013-12-04
, 20:05
|
|
Posts: 50 |
Thanked: 100 times |
Joined on Jan 2012
@ Tampere, Finland
|
#10
|
Originally Posted by coderus
Because the application needs to synchronize it's state to a remote server when it is closed.
why you need this?
Originally Posted by coderus
I have been planning to make a separate daemon and ui, but due to limited time available i am not going to do this anytime soon.
isnt better to rewrite logics?
set event filter, catch close event, do whatever.
I'd be even happy to write a patch to Qt or Sailfish itself if it is the only way and would be accepted into upstream.
I'm writing an application which has to do dome network operations after user has closed the UI. Normally this is not possible, as the applications Qt main loop exits when closing the UI.
On Harmattan i found a workaround - re-starting the mainloop by calling QGuiApplication::exec(). This seems to crash on Sailfish.
The next workaround i tried to use is to create an event filter for the QGuiApplication and try to filter out the close event. QEvent::Close never happens, but QEvent::ApplicationDeactivate does. It can be used to prevent killing main loop, but unfortunately it also happens when user swipes the application to the background.
Any ideas on how can i accomplish this?