How to stucture fullscreen Raspberry Pi application with screen transitions?

[anda_skoa]

My overall suggestion would be to go for QtQuick (QML) for this type of interface.

Transitions like that are easy to do with QtQuick animations but a lot of work with widgets.

Each screen can then be done as a separate QML obejct/file, transitions could potenially be delegated to a StackView.

Cheers,
_

[dgb589]

@anda_skoa Thank you. Following your advice, I looked into Qml and I admit it that, using StackView, one might achieve transitions easily. However, I originally forgot to add that the application will neither have a touch screen nor a mouse. In fact, it will be controlled by several hardware buttons, such as keyUP, keyDown, keyRight, keyLeft, btnAccept, etc... It seems to me that QtQuick is perfect for the scenario in which there is a touch screen or a mouse available - scrollable Views, drawers, check boxes etc. fit perfectly then. However, due to the control limitations I am facing, the flow will be the following:

the user will navigate between buttons on the screen by pressing left, right, up and down to hover over a given button and then press the accept button to simulate the button press. In that scenario, it seems to me that many of the functionalities that QML provides are not used. For instance, a scrollable list view cannot be incorporated since it depends on scrolling motion, which cannot be done using the hardware buttons that I will implement.

Do you think that my concerns are legitimate or would you still continue with QML? Thank you!

[anda_skoa]

While the components are touch aware, I don't see any problem when not using that.

E.g. you can scroll the listview programmatically, on press of a button, keyboard key, hardware button or dial.

A lot of the QtQuick based HMIs for cars, machine control interfaces, etc., use hardware controls as input devices, some exclusively, some in addition to touch screen capability.

Cheers,
_