44r0n7/mangotune
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Sync HUD Order page after profile restore/apply #8

New Issue
Closed
opened 2026-03-31 03:45:53 +00:00 by 44r0n7 · 1 comment
44r0n7 commented 2026-03-31 03:45:53 +00:00
Owner
Copy Link
Copy Source

After applying/restoring one of MangoTune's saved profiles, the actual HUD order from that profile is reflected correctly in the running preview, but Tools -> HUD Order does not show the same order.

Observed behavior:

  • Apply/restore a saved profile whose config file has a known non-default HUD order.
  • The preview updates and shows the expected restored order.
  • Open Tools -> HUD Order.
  • The list shown there does not reflect the restored order from the active config.

This looks like a UI state/derived-order mismatch rather than MangoHud ignoring the order, because the preview itself is correct.

Likely investigation points:

  • HUD Order page may be rebuilding from stale state after profile apply/restore.
  • The page's visible-group order derivation may not be re-run after config replacement.
  • Profile restore/apply may update preview/runtime state without fully refreshing the page model.

Acceptance criteria:

  • After profile apply/restore, HUD Order immediately shows the same order that the preview and current config now use.
  • No manual page switching or extra apply step should be required.
After applying/restoring one of MangoTune's saved profiles, the actual HUD order from that profile is reflected correctly in the running preview, but `Tools -> HUD Order` does not show the same order. Observed behavior: - Apply/restore a saved profile whose config file has a known non-default HUD order. - The preview updates and shows the expected restored order. - Open `Tools -> HUD Order`. - The list shown there does not reflect the restored order from the active config. This looks like a UI state/derived-order mismatch rather than MangoHud ignoring the order, because the preview itself is correct. Likely investigation points: - `HUD Order` page may be rebuilding from stale state after profile apply/restore. - The page's visible-group order derivation may not be re-run after config replacement. - Profile restore/apply may update preview/runtime state without fully refreshing the page model. Acceptance criteria: - After profile apply/restore, `HUD Order` immediately shows the same order that the preview and current config now use. - No manual page switching or extra apply step should be required.
44r0n7 commented 2026-03-31 20:34:02 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. HUD Order now reflects the restored/applied profile order correctly again, and the related HUD Order navigation/live-update regressions addressed in the same pass are stable with cargo fmt --all, cargo test -q, and cargo clippy --all-targets -- -D warnings passing.

Resolved. `HUD Order` now reflects the restored/applied profile order correctly again, and the related HUD Order navigation/live-update regressions addressed in the same pass are stable with `cargo fmt --all`, `cargo test -q`, and `cargo clippy --all-targets -- -D warnings` passing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
44r0n7
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: 44r0n7/mangotune#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?