I've not found this function after a lot of use, so I'm making the assumption that it's not present.

What I'd like to suggest, is the ability to define separate "Screens" in a single integrated UiFlow Program.

This would operate somewhat like an old "HyperCard" stack, where each "screen" has a separate and defined UI that can be set up via the UiFlow editor.
(Navigation between screens during coding could be added just above the "Units" Selector)

To keep code clean, there could be a "screen 0" that contains code that is present across the whole project (e.g. Wifi Connections, MQTT, Global Variables) and sets instructions for an initial screen display or which screen to switch to.
Screens are traversed via blocks that instruct which screen to switch to, which could be tied to events or button presses.
Events/Functions can be triggered by switching into screens (Much like Setup is used per project) or switching away.

This simple change could clean up messy projects that rely on code to move the screen around, enhance projects that are data driven, make UI design simpler and more intuitive and add a world of function and the opportunity for more complexity into this simple software.

I've not found this function after a lot of use, so I'm making the assumption that it's not present.

What I'd like to suggest, is the ability to define separate "Screens" in a single integrated UiFlow Program.

This would operate somewhat like an old "HyperCard" stack, where each "screen" has a separate and defined UI that can be set up via the UiFlow editor.
(Navigation between screens during coding could be added just above the "Units" Selector)

To keep code clean, there could be a "screen 0" that contains code that is present across the whole project (e.g. Wifi Connections, MQTT, Global Variables) and sets instructions for an initial screen display or which screen to switch to.
Screens are traversed via blocks that instruct which screen to switch to, which could be tied to events or button presses.
Events/Functions can be triggered by switching into screens (Much like Setup is used per project) or switching away.

This simple change could clean up messy projects that rely on code to move the screen around, enhance projects that are data driven, make UI design simpler and more intuitive and add a world of function and the opportunity for more complexity into this simple software.

I've run into similar issues, I have elements on the StickC that disappear or only work with certain fonts, the UI designer itself won't let me place items on parts of the StickC screen, and whole chunks of code don't run.

I've worked around it for now in my Test Application, but this is a serious problem for anyone trying to build something complex.

Most cases, I've had to shift the location of the MQTT code in the python in order to activate parts of the on screen functionality, seems like maybe a library is conflicting or interfering with the rest of the code.

Are we going to see another version?

I've been hunting for something like this for years, and I stopped checking for a few months, just to find you'd released and discontinued the product during that short window I was away!

I would gladly pay to get a new version, and I can see more uses for this product than most other parts of the M5 Lineup.
As it is I'm paying a premium to get a model from a distributor with leftover stock.