The Qt event loop is tied to your Activity. An Android app can have several
activities (which are UIs) and services. Android can kill your app at anytime,
you're supposed to stave your UI state inva bundle and restore it when it's
needed again, as per lifecycle events. It's annoying.
> Sent: Sa
Hi Alexander,
I'm not an Android expert nor have I written a Qt/Android application other
than small demos but what I remember from Java/Android application
lifecycle, an application consists of "activities" that may be
paused/unloaded/terminated by the operating system at any time due to
various
Sorry, forgot to mention that i'm using
QGuiApplication::setQuitOnLastWindowClosed(false). So Qt should not call
quit for me... (as I was thinking).
On 11/30/2019 3:36 PM, Alexander Dyagilev wrote:
Hello,
It seems that my app "suffers" from unexpected terminating of
QCoreApplication::exec()
Please note that this problem happens on a specific devices only. We
can't reproduce it on our Android smartphones.
On 11/30/2019 3:36 PM, Alexander Dyagilev wrote:
Hello,
It seems that my app "suffers" from unexpected terminating of
QCoreApplication::exec() event loop processing.
I was alw
Please see my "Android: can QCoreApplication::exec() be terminated
unexpectedly?" question :)
On 11/30/2019 3:26 PM, Alexander Dyagilev wrote:
I will ask about a bit later :)
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-projec
Hello,
It seems that my app "suffers" from unexpected terminating of
QCoreApplication::exec() event loop processing.
I was always thinking that QCoreApplication::exec() terminates only if
one calls QCoreApplication::quit().
But under Android it seems that either QCoreApplication::quit() is
Hello,
It seems, the problem is solved (partially).
In my classes I was keeping QThread instance inside of QScopedPointer
object. All these my classes has deinitialization method, which was
calling QThread::quit, QThread::wait and releasing the pointer.
I removed QScopedPointer and started t
