Christian Strømme f8cc0164db Android: Always queue calls from Qt to Android. ... Calling runOnUiThread() only queues calls that comes from a different thread then the UI thread. The problem with the current solution is that we can't promise or rely on the calls being delivered in the same order they were called. Another consequence of the old behavior is that we potentially cause long lasting synchronization points, which can cause the application to become unresponsive or in worst case result in a deadlock. With this change all calls to runAction() will be queued on Android's main message queue (aka the UI thread) and return immediately. Change-Id: I50a4273ae9ba8ad17fb2c50ccd57449e4fbc12f9 Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>		2015-09-15 13:23:57 +00:00
..
accessibility	Android: Delay initialization of Accessibility.	2015-06-09 09:06:39 +00:00
jar	Android: Always queue calls from Qt to Android.	2015-09-15 13:23:57 +00:00
java	Fix typo in local variable name	2015-09-13 14:56:53 +00:00
templates	Android: Fix resuming app after locale change	2015-06-02 07:28:43 +00:00
android.pro	Do not initialize accessibility code by default on startup.	2014-12-09 16:59:03 +01:00