fix(#429): debounce 0x91 channel-change push to coalesce burst re-syncs
Gemini review (standards#145) flagged that a burst of 0x91 pushes (e.g. a bulk channel edit on the device) would each trigger a full getChannels re-sync. getChannels already guards concurrent syncs (_isSyncingChannels), so there is no request flooding, but sequential re-syncs after each completes would repeatedly clear+repopulate the channel list (UI flicker). Coalesce the burst with a 400ms debounce so it settles into a single re-sync. Timer is cancelled in dispose(). Citadel: meshcore-open-p12fix/445-windows-sqlite3-native-assets
parent
e8c756718a
commit
6480034a63
Loading…
Reference in new issue