Details
-
User Story
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
None
-
Android
-
2023wk44FOQtforAndroid, 2023wk46FOQtforAndroid, 2023wk48FOQtforAndroid
-
ac7f22ed0 (dev), 820cf7fbc (dev), 457566c96 (dev), 58c7249ee (dev), 0f3dbd6dc (dev), 426524550 (dev), 19baa077d (dev), 23499e784 (dev), f5e230285 (dev), d6861926a (dev), 50b56d015 (dev), fa15a465e (dev), 833e7c162 (dev), 869e9b927 (dev), c8bf35f4e (dev)
Description
Currently many part of the Android QPA live under QtNative where functionalities are treated as static one Activity based app. This can be improved by moving them into separate classes handling specific functionality tied to each Activity instead.
The various parts identified so far:
Input management (keyboard, touch, mouse)- Clipboard
- Display and screen
- Library loading mechanism (this is handled under
QTBUG-115016) - Accessibility
- Surface and rendering management
- Event management
Attachments
Issue Links
- covers
-
QTBUG-119007 Android: QtDisplayManager.onDisplayChanged() can lead to a null pointer exception
-
- Closed
-
- mentioned in
-
Page Loading...