You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a project using FZ sample apps as a reference, and I've encountered a challenge with scene management and creating menus. Despite studying the source code of these apps written in C, I'm having difficulty understanding how scenes are structured, how menus are implemented, and how to manage the flow between different scenes.
My goal is to develop an application with four distinct screens:
HomeScreen: Contains an "Ok" button that transitions to the next screen.
Menu Screen: Features two buttons, each leading to a separate scene.
Scene1: Displays the simple text "Scene1".
Scene2: Displays the simple text "Scene2".
I'm familiar with creating a single scene, but I'm unsure about how to expand this into full scene management to allow for seamless navigation through the app. Specifically, I want to enable users to move between screens using "OK" and "back" buttons, with the ability to exit the application only from the HomeScreen. Any other screen should return the user to the previous screen.
In the C examples I've reviewed, there's typically a scenes/ folder containing separate .c and .h files for each scene. I'd like to adopt a similar structure for my project, which is in Rust, something like:
Although I've seen examples covering scene management and menus/submenus, they are often deeply intertwined with complex C code, making it hard for me to extract the parts relevant to my needs.
Could anyone provide a simplified example or guidance on how to handle scene management and menus? Any help would be greatly appreciated as it would significantly aid my learning process.
This discussion was converted from issue #136 on March 20, 2024 06:33.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm currently working on a project using FZ sample apps as a reference, and I've encountered a challenge with scene management and creating menus. Despite studying the source code of these apps written in C, I'm having difficulty understanding how scenes are structured, how menus are implemented, and how to manage the flow between different scenes.
My goal is to develop an application with four distinct screens:
HomeScreen: Contains an "Ok" button that transitions to the next screen.
Menu Screen: Features two buttons, each leading to a separate scene.
Scene1: Displays the simple text "Scene1".
Scene2: Displays the simple text "Scene2".
I'm familiar with creating a single scene, but I'm unsure about how to expand this into full scene management to allow for seamless navigation through the app. Specifically, I want to enable users to move between screens using "OK" and "back" buttons, with the ability to exit the application only from the HomeScreen. Any other screen should return the user to the previous screen.
In the C examples I've reviewed, there's typically a scenes/ folder containing separate .c and .h files for each scene. I'd like to adopt a similar structure for my project, which is in Rust, something like:
Although I've seen examples covering scene management and menus/submenus, they are often deeply intertwined with complex C code, making it hard for me to extract the parts relevant to my needs.
Could anyone provide a simplified example or guidance on how to handle scene management and menus? Any help would be greatly appreciated as it would significantly aid my learning process.
Beta Was this translation helpful? Give feedback.
All reactions