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

Decide how saved-config live updates should relate to in-memory preview refresh #2

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

Saving the real MangoHud config while a game or vkcube is running updates the real MangoHud overlay directly.

Open product/tech question:

  • should MangoTune keep the current in-memory live refresh model for unsaved changes
  • or should it lean more on real saved-config updates for true live behavior
  • if in-memory changes cannot behave the same way, should the app reduce or simplify the current live-refresh idea

Open angle to investigate:

  • whether MANGOHUD_CONFIG / MANGOHUD_CONFIGFILE style flows can help bridge this
  • how preview-only FPS/runtime controls should coexist with whatever model we choose
Saving the real MangoHud config while a game or `vkcube` is running updates the real MangoHud overlay directly. Open product/tech question: - should MangoTune keep the current in-memory live refresh model for unsaved changes - or should it lean more on real saved-config updates for true live behavior - if in-memory changes cannot behave the same way, should the app reduce or simplify the current live-refresh idea Open angle to investigate: - whether `MANGOHUD_CONFIG` / `MANGOHUD_CONFIGFILE` style flows can help bridge this - how preview-only FPS/runtime controls should coexist with whatever model we choose
44r0n7 commented 2026-03-31 21:25:36 +00:00
Author
Owner
Copy Link
Copy Source

Recent progress: preview update behavior is now documented in docs/PREVIEW_UPDATE_MAP.md, and the code paths were partially centralized around shared preview apply helpers in src/ui/pages/mod.rs (commits 7e95b7f and a36c02b). This narrows the remaining work in this issue to the product/architecture decision itself: how saved-config live updates should coexist with or replace the in-memory preview-refresh model.

Recent progress: preview update behavior is now documented in docs/PREVIEW_UPDATE_MAP.md, and the code paths were partially centralized around shared preview apply helpers in src/ui/pages/mod.rs (commits 7e95b7f and a36c02b). This narrows the remaining work in this issue to the product/architecture decision itself: how saved-config live updates should coexist with or replace the in-memory preview-refresh model.
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#2
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?