Fix touchscreen navigation and add runtime touch diagnostics
This commit is contained in:
1 parent
23fe7c8a9d
commit
14796e6573
32 files changed
+1785
-123
No files matched your search
@@ -83,6 +83,7 @@ over the normal binary USB, BLE, or TCP connection:
|
||||
| [`get/set wifi.powersave`](cli_commands.md#browser-configuration-portal-esp32-repeater-and-room-server) | ESP32 WiFi Companion; active transport constraints still apply |
|
||||
| [`get/set bluetooth.name`](cli_commands.md#view-or-change-the-independent-bluetooth-name-companion) | Companion firmware |
|
||||
| [`get/set bluetooth.mac`](cli_commands.md#view-or-change-the-bluetooth-address-ble-companion) | Every Companion build with Bluetooth |
|
||||
| [`get/set display.touch`](cli_commands.md#show-touchscreen-touch-areas) | Touchscreen Companions using the shared UI; text terminal and framed CLI; off after reboot |
|
||||
| [`uf2reset`](cli_commands.md#enter-the-uf2-bootloader-nrf52-only) | Every nRF52 Companion text terminal and local command `0x42`; local only |
|
||||
|
||||
Deprecated binary aliases remain receive-only for older clients; new clients
|
||||
|
||||
@@ -713,6 +713,31 @@ board's compiled default. Unsupported display drivers return an error.
|
||||
|
||||
---
|
||||
|
||||
## Show touchscreen touch areas
|
||||
|
||||
All touchscreen Companion builds using the shared touch UI support temporary
|
||||
diagnostic outlines, including both SenseCAP Indicator rendering sizes:
|
||||
|
||||
```text
|
||||
get display.touch
|
||||
set display.touch on
|
||||
set display.touch off
|
||||
```
|
||||
|
||||
The default is **off at every boot**. Enabling wakes the display without
|
||||
selecting anything. Dotted yellow borders mark the actual scaled tap targets;
|
||||
the area under a held finger turns green and returns to yellow on release.
|
||||
Disabling removes the borders on the next redraw. Pairing screens suppress the
|
||||
overlay while they consume navigation. This option does not change the font,
|
||||
touch calibration, navigation actions, or saved settings, and is not persisted.
|
||||
|
||||
Use the text terminal or Companion framed CLI (`0x42`) through an available
|
||||
USB, BLE, or TCP connection. Non-touchscreen, missing-display, and legacy UI
|
||||
builds report `Error: touchscreen diagnostics unsupported`. No Indicator-only
|
||||
build flag is needed.
|
||||
|
||||
---
|
||||
|
||||
## Set MQTT observer display timeout and flip
|
||||
|
||||
MQTT observer builds with a display support a persisted inactivity timeout:
|
||||
|
||||
Reference in new issue
Block a user