ui: one badge per enabled signal, an N signals overflow, and the order kept in memory
This commit is contained in:
1 parent
ad5e30f338
commit
f27925da59
6 files changed
+213
-3
No files matched your search
@@ -451,6 +451,10 @@ precedent, not an exception.
|
||||
per-signal `signal:<name>` slide-over pages. **Against a config that has already seen the tour** (a first run's
|
||||
auto-tour closes the slide-over at about 1.5 s, which is when this probe opens its page). One `[signalpage]` line;
|
||||
see [probe-readings.md](probe-readings.md).
|
||||
- `UDPSCOPE_PROBE_SIGNAL_BADGES_MS=1500` with `UDPSCOPE_EXIT_AFTER_MS=5000` and `UDPSCOPE_ENABLE_ALL_MS=500` -- the
|
||||
signal badges in the badge bar. **Against a config that has already seen the tour**, as above (the probe clicks
|
||||
the badges, and the auto-tour would close the page). One `[sigbadges]` line; see
|
||||
[probe-readings.md](probe-readings.md).
|
||||
- `UDPSCOPE_PROBE_BADGES_MS=2000` with `UDPSCOPE_EXIT_AFTER_MS=5000` and `UDPSCOPE_ENABLE_ALL_MS=500` -- the badge
|
||||
bar under the plot. One `[badges]` line, which must read `table_bad=0 fixed=1 open_marked=1 page_open=1
|
||||
closed_unmarked=1`: `table_bad` counts the rows of the 16-input `trigger_badge_state()` table the probe
|
||||
|
||||
Reference in new issue
Block a user