Jakub e354b78b46 fix(nav): ping result never appeared after Send ...

startPingForKey() set the "RTT: ..." line but didn't rebuild the ping
menu, and updatePingMenuState only rebuilt on a string-count change it
computed after the mutation — so the menu stayed at a lone "Send" row and
nothing visibly happened after pressing Send, whether or not a reply came.

- Rebuild the menu right after starting the ping so "RTT: ..." shows at
  once; on send failure show "RTT: send fail" instead of a blank.
- Sync the menu against its actual row count (_ping_menu._count) as result
  lines populate, so RTT/SNR rows appear when the reply lands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-03 14:11:03 +02:00

..

companion_radio

fix(nav): ping result never appeared after Send

2026-06-03 14:11:03 +02:00

kiss_modem

simplify kiss noise floor sampling

2026-02-07 07:42:52 -08:00

simple_repeater

* version 1.15.0

2026-04-19 11:27:55 +10:00

simple_room_server

* version 1.15.0

2026-04-19 11:27:55 +10:00

simple_secure_chat

Merge pull request #1297 from ViezeVingertjes/feature/duty-cycle-token-bucket

2026-03-08 23:54:32 +11:00

simple_sensor

Merge branch 'default-scope' into dev

2026-04-17 16:30:19 +10:00