Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.8.0 Beta3
-
-
2024wk38s2FOQtforAndroid
Description
Our commercial customer is heavily relying on QtNative.activity() in their application's Java code to get handle to the main activity. They have their own activity which extends org.qtproject.qt.android.bindings.QtActivity and that is registered in the manifest. They need to be able to get a handle to their main activity from other places of Java code located in different submodules/libraries.
What is the motivation of changing access level of formerly public QtNative.activity() API? Qt 6.8 still being in beta level would it be possible to change is back to public?