Really like this idea — "boot the cab, Repair makes sure there are no surprises" is a great way to frame it, and the flipper-controlled prompt + revocable auto-confirm list is a smart UX for a cab where you don't always have a keyboard/mouse handy.
Being honest about scope though: this is a bigger piece of work than it might look like. Everything Repair does today runs when you open the app and click something — this would mean Repair (or a companion piece of it) acting at boot time, plus building a whole new in-game-style prompt that reads flipper button input, which nothing in the project does yet. I want to actually research how to do the flipper-input part properly rather than bolt something fragile together.
So: not going to promise a date, but it's logged and I think it's worth building right. If you (or anyone else reading this) knows how other tools intercept flipper/cab button input outside of VPX or Popper itself, I'd genuinely like to hear about it — that's the main unknown right now.
Thanks for putting real thought into this, appreciate it.
Top
are all trademarks of VPFORUMS.