-
Technical task
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Why?
Cause Qt Quick for Android APIs work with Kotlin and Java, but the examples and such are done with XML based approach. As examples are developed with Qt folks, they are also made with Qt Commercial licenses, but the offering is for open source users as well. We want to see how the APIs will work with Jetpack Compose based application written with open source license __
What?
Definition How an open-source license developer brings an interactive Qt Quick 3D model to the user interface of an Android app implemented with Jetpack Compose (current support and shortcomings & suggestions for improvement). Expect a written report with written shortcomings and suggestions for improvement to be plastered on https://bugreports.qt.io/ and a sample project on github.
Demarcation Sample project does not need to be an official example
- resulted in
-
QTBUG-138985 QtQuickView loses it's real-time updating when a composable element pops over it
-
- Reported
-
-
QTBUG-139006 QtMainLoopThread crashes on x86_64 android emulator due to graphics backend initialization fail
-
- Reported
-
-
QTBUG-139098 AndroidView with QML content gets replaced by non-existing window upon recompose
-
- Reported
-
-
QTBUG-139081 Android: QQuickView doesnt render with Jetpack Compose navigation outside startDestination
-
- Reported
-
-
QTBUG-139173 Android: View3D zooms in to bottom left after switching Activities
-
- Reported
-
-
QTBUG-138941 Android: Improper QQuickView Reuse across screens
-
- Open
-
-
QTBUG-138922 Consistent Qt caused crash when navigating with Jetpack Compose
-
- Closed
-