Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
6.8.0
-
None
Description
QtQuick3D.Xr handles XrSessionStates mostly internally, which is fine for states like XR_SESSION_STATE_READY (start rendering), XR_SESSION_STATE_EXITING (immediately exit) and XR_SESSION_STATE_LOSS_PENDING (prepare for exit), but it is pretty important for the apps to know when they are ready for interaction (XR_SESSION_STATE_FOCUSED) and when they are otherwise visible but e.g. some modal system dialog is blocking user input (XR_SESSION_STATE_VISIBLE) and the app is in the background so they can pause animations and heavy operations and e.g. bring up the pause menu.
Also not sure how Qt text input and/or key event delivery is supposed to work in XR environment without any QWindow and concept of focus object. Text input is pretty central use case for any non-trivial apps. OpenXR provides no support there, but leaves that for the client (Qt) side.