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
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Saving the real MangoHud config while a game or
vkcubeis running updates the real MangoHud overlay directly.Open product/tech question:
Open angle to investigate:
MANGOHUD_CONFIG/MANGOHUD_CONFIGFILEstyle flows can help bridge thisRecent 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
7e95b7fanda36c02b). 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.