This is in response to:
https://forums.homecomingservers.com/topic/38674-bindcontrol-keybinds-and-popmenus-editor-and-manager/page/8/#findComment-757366
The notion here being that, as a separate type of file (*.bco?), the user could save an Overlay Profile, which contains the minimal set of changes that they have explicitly done. When loading this profile, the Default Profile would be loaded first, and then the Overlay splatted on top. Then changes to the Default Profile could be "inherited" by any Overlay that hadn't changed the same thing itself.
A few UI concerns:
- this is a fiddly thing to explain and would probably want a new button on the front page and several new menu items.
- The profile would have to keep, off to the side, a list of every control it's changed explicitly. This would have to be managed pretty diligently, not through like "UpdateData()" or something, in order to keep side effects from "leaking" into the overlay.
- Would we want some way to mark up controls that are part of the overlay? That seems -very- fiddly and fraught.
More to ponder.
This is in response to:
https://forums.homecomingservers.com/topic/38674-bindcontrol-keybinds-and-popmenus-editor-and-manager/page/8/#findComment-757366
The notion here being that, as a separate type of file (*.bco?), the user could save an Overlay Profile, which contains the minimal set of changes that they have explicitly done. When loading this profile, the Default Profile would be loaded first, and then the Overlay splatted on top. Then changes to the Default Profile could be "inherited" by any Overlay that hadn't changed the same thing itself.
A few UI concerns:
More to ponder.