Add TX16S UI harness#7337
Open
onliner10 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: N/A
Summary of Changes
This adds a repeatable TX16S UI automation harness for simulator-driven UI work.
The goal is to make future color LCD/touch UI changes easier to review, easier to automate, and safer to regression-test before touching production UI code.
Why This Is Being Added
EdgeTX UI work currently depends heavily on manually launching the simulator, navigating screens by hand, and capturing host-window screenshots. That makes visual regression checks hard to repeat and easy to skew by local window scale, focus, or setup state.
This harness provides a small, opt-in control plane around the existing simulator so contributors can build, navigate, and capture framebuffer screenshots in a reproducible way.
It also makes EdgeTX much easier to work on with AI coding agents. The simulator can be exposed as an MCP server, so an agent can start a TX16S simulator session, press keys, rotate, tap, wait, capture screenshots, and inspect UI state without relying on manual host-window interaction. That should make UI work more reviewable and less speculative.
This is intended as groundwork for future TX16S-class color touchscreen UI improvements. It does not redesign the UI and does not change model storage, EEPROM format, Lua APIs, or normal simulator behavior.
What Changed
--automation-stdioto the SDL simulator as an opt-in automation mode.status, key press, long press, rotary, touch, wait, screenshot, and stop.simuLcdCopy, avoiding host-window screenshots.tools/ui-harness/edgetx-uiCLI for build, smoke, and JSON flow execution.tools/ui-harness/edgetx-mcpas a stdio MCP wrapper using the same Python core as the CLI.home,menu, andreturn-homescreenshots.uvproject metadata so contributors can run the harness with a known Python dependency set.EDGE_TX_BUILD_TESTSso this harness build path can avoid fetching/building native tests when they are not needed.Contribution / Review Notes
--automation-stdiois passed.EDGE_TX_BUILD_TESTSoption only disables them when explicitly set toOFF.PCB=X10,PCBREV=TX16S), but the harness is structured so more color LCD/touch targets can be added later.Verification
The smoke flow produced three valid 480x272 PNG screenshots from the simulator framebuffer:
homemenureturn-home