PROS 4.1: Virtualize screens for templates

[Richard-Stump]

Potential Problem

With the idea of branchline, there's the potential for templates that utilize the screen to conflict. For example, there was talk about using the screen to display some values while testing robots for BLRS, but our ARMS template uses the whole screen for it's auton selector feature. This issue is likely not a huge one at the moment, but I think when we release branchline that it could become bigger as users have easier access to templates.

Solution:

Virtualize screens for templates (and maybe user programs) so that every template can provide some sort of UI on the V5 screen without conflict. Provide a UI where the user can switch between the virtual screens for the different templates. This would decrease the screen real-estate some, but would effectively increase the screen real-estate by letting each template have a screen.

Another idea would be to let templates/programs request additional virtual screens, and then they could utilize multiple screens of data.

UI Mockup Idea 1 (not to scale):

UI Mockup Idea 2 (not to scale):

Potential issues:

• Will this cause issues with LVGL
• What about the LVGL decouple?

[SizzinSeal]

@unwieldycat has made a PROS 4 template that solves this: robodash.

Any template that uses its view API can add its screens to a slide-out menu that persists between screens