dandri/ZephCore
1
0
Fork 0
mirror of https://github.com/liquidraver/ZephCore.git synced 2026-09-01 21:08:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

joystick UI: "Reset path" now actually forces flood

Browse Source 
The contact submenu's reset-path action set out_path_len = 0, which
means "direct, 0 hops" — formatHopCount rendered the contact as
"direct" and sendMessage would still try direct send. Use
OUT_PATH_UNKNOWN (0xFF) so the next DM floods and rediscovers the
path. Also schedule a contacts flush (markContactsDirtyPublic) so
the reset survives reboot — previously the change was in-memory only.
This commit is contained in:
liquidraver
2026-05-21 22:34:10 +02:00
parent e778326ad0
commit 516536db1c
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
zephcore/helpers/ui-joystick/screens/contacts.cpp
+10 -1
View File
@@ -559,7 +559,16 @@ bool ContactsScreen::handleInput(char key)
if (_submenu_selected == _idx_reset_path) {
ContactInfo *live = _task->getMesh()->lookupContactByPubKey(
_active_contact.id.pub_key, PUB_KEY_SIZE);
if (live) { live->out_path_len = 0; memset(live->out_path, 0, sizeof(live->out_path)); }
if (live) {
/* OUT_PATH_UNKNOWN (0xFF) marks "no saved path → flood".
* Plain 0 would mean "0-hop direct" and the contact would
* render as "direct" instead of forcing a flood-rediscover. */
live->out_path_len = OUT_PATH_UNKNOWN;
memset(live->out_path, 0, sizeof(live->out_path));
if (CompanionMesh *cm = static_cast<CompanionMesh *>(_task->getMesh())) {
cm->markContactsDirtyPublic();
}
}
_task->showAlert("Path reset", 800);
return true;
}