feat: split kiosk into fallback canvas and OSD overlay layers (#8)

Drive two independent visual layers per display target from one shared
video presence signal: the fullscreen fallback/menu canvas below video
and a transparent, input-transparent OSD overlay above video, reserved
as the future flight OSD rendering surface. WFB and video decode stay
out of the UI process; pilot video keeps rendering priority.
This commit is contained in:
2026-10-01 15:43:31 +02:00
parent b169a64ad5
commit c911872de5
9 changed files with 674 additions and 114 deletions
+2 -2
View File
@@ -7,8 +7,8 @@ Orange Pi Zero 3W application for the custom OpenIPC/WFB ground station.
- receives framed GX12 RC channel data over the dedicated AUX1 UART at 115200 8N1;
- validates protocol version, frame length and CRC-16;
- logs final mixed channel values;
- starts an independent kiosk display process that maps a fullscreen black canvas on `DISPLAY=:0` before video, tolerates X11 downtime without restarting the supervisor, and stops deterministically on shutdown;
- video keeps rendering priority: the kiosk canvas stays below the `fpv-video` window, shows the exact fallback text `Brak połączenia WFB` only while no video output is presented, and future display targets (MIPI/touch) get their own target-specific templates instead of one global layout.
- starts an independent kiosk display process that maps two independent layers on `DISPLAY=:0` for the Viture target before video: the fullscreen fallback/menu canvas below video, and a transparent, input-transparent OSD overlay above video reserved as the future flight OSD rendering surface; both tolerate X11 downtime without restarting the supervisor and stop deterministically on shutdown;
- video keeps rendering priority: the kiosk canvas stays below the `fpv-video` window, shows the exact fallback text `Brak połączenia WFB` only while no video output is presented, and the OSD overlay stays above video without ever presenting pixels over it or intercepting its input; future display targets (MIPI/touch) get their own target-specific templates instead of one global layout.
The first baseline is intentionally small. It does **not** yet control an AUX, manipulate the flight-control link, or replace the primary video pipeline.