| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The JNI utilities (i.e. QJniObject, QJniEnvironment) are already under
qtbase as public APIs.
Permission handling is now under QCoreApplication::{check,request}Permission
and QPermission namespace.
Some of the QtAndroid namespace functions are now under QNativeInterface's
QAndroidApplication, this includes:
* sdkVersion()
* hideSplashScreen()
* context() and isActivityContext()
* runOnAndroidMainThread()
The remaining APIs are now moved as private APIs under qtbase
ee05af296f65e240f64db6470cdddafbddbf2fa3. That is until we add
new cross-platform APIs to replace their functionalities like
Intents handling, starting activites and working with Services.
Task-number: QTBUG-83251
Task-number: QTBUG-84382
Pick-to: 6.2
Change-Id: Id077f8cbbe223a987916f737fad6088fb58e470d
Reviewed-by: Ville Voutilainen <ville.voutilainen@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-73409
Change-Id: I994fb873c140a13151bde4ef065fd21f22701b93
Reviewed-by: Ville Voutilainen <ville.voutilainen@qt.io>
|
|
|
|
|
|
|
|
|
| |
The current way of handling activity results by inheriting from QAndroidActivityResultReceiver
is very un-Qt. This patch allows handling activity results by passing a std::function/lambda
expression to the startActivity function.
Change-Id: Ie9dc91cd02dfcdb16a9ad0cb7858387e75159815
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The function simply calls the other startActivity with
QAndroidIntent::handle, anyone could do that from the user code, but i
think it makes sense the library to allow you doing this directly given
you're supposed to pass an intent and we have a class that represents an
intent
Change-Id: I673cb410b07ed4fd1408a971696a3b5ae3dfd063
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
|
|
|
|
| |
Task-number: QTBUG-50759
Change-Id: Ie7fef30049e6be28c3fba2eb5b54b56552df8c9d
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
These are the building blocks for higher level APIs such as Qt Remote
Objects.
[ChangeLog][Android] Added low level APIs for Android Service & Binder.
Change-Id: I320214d310a398541bbde985ecf67bf6101c0b67
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
|
|
|
|
|
| |
Change-Id: If78fe57fd5ceccad541fb2b3d7a92eefcda06057
Task-number: QTBUG-59200
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
|
|
|
|
|
|
| |
[ChangeLog][QtAndroidExtras][QtAndroid] Added QtAndroid::androidContext()
Task-number: QTBUG-55102
Change-Id: I95122c8939e227acffb13ea9ba1a338a9d05595a
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
|\
| |
| |
| | |
Change-Id: I3d3f2f84808ca29a056783873dd78094a53c2875
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
... or equivalent.
QtBase 5.6 headers already compile that way, so let the other
modules follow suit.
Change-Id: I26201944b21d83f78c9e1c75cbd55334cd16359f
Task-number: QTBUG-45291
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
| |
| |
| |
| |
| |
| |
| | |
This function is useful to hide a sticky splash screen.
Change-Id: I724a47a8cb73d3288916ed77b760217520d6b5ef
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Currently accessing the service requires use of private APIs.
Change-Id: I480657978e8318f98f5ee24bd4587c467110677a
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add two function to allow the users to easily run (a)synchronously Runnables from any thread
directly to Andoroid UI thread. These functions are useful to create java controls and to access
their methods, which must done on Android UI thread.
Change-Id: Iec5437321e6136cc90268cc7ecf091f82fc4cdd3
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
|/
|
|
|
|
|
|
|
|
| |
From Qt 5.7 -> LGPL v2.1 isn't an option anymore, see
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
Updated license headers to use new LGPL header instead of LGPL21 one
(in those files which will be under LGPL v3)
Change-Id: I8bec15fbd91b483adb0f9e24878a701e9fb0061d
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.
Change-Id: Id0bb1fd5a9d695520753a280bb1ad5ba1ccc6026
Reviewed-by: Sergio Ahumada <sahumada@texla.cl>
|
|
|
|
|
|
|
|
|
|
| |
- Renamed LICENSE.LGPL to LICENSE.LGPLv21
- Added LICENSE.LGPLv3 & LICENSE.GPLv2
- Removed LICENSE.GPL
Change-Id: Iad800f28f4e85e3f00512400ed9c5ed196c5097a
Reviewed-by: Antti Kokko <antti.kokko@digia.com>
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need an API for this, because otherwise it would be
impossible to start intents and get results from them
without having access to the application's activities.
For third-party libraries etc., this is required.
When we define a public Java API, we will implement a similar
API there, so that applications can also start intents from
Java code without worrying about collisions with third-party
add-ons.
[ChangeLog][Intents] Introduced API to launch intents.
Change-Id: Ic3bbfbbaced3278c2ee970e74cba2997d5d867c4
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The Android SDK version, or API level, is commonly used to determine
what APIs are available at runtime.
[ChangeLog][QtAndroidExtras] Added convenience method for getting the
Android SDK version.
Change-Id: Ic20322f68bc9680aec9e1c8404583462063904db
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
There were no public APIs the user could use to get access to
their applications main activity, and thus far the only solution have
been to access undocumented and private APIs.
[ChangeLog][QtAndroidExtras] Added functionality to get the Android main
activity.
Change-Id: Ifd4121e8bc643360ed7a7038ffae9e872b59db71
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
|