Problem:
I have profiles for multiple games and apps, and they're usually lightly modified copies of my Default profile, with one or two bindings changed.
However, whenever I make a change to an input my Default profile, I then have to redo that change across ALL of my other profiles where I intend for that input to be identical. That can get pretty tiresome, especially if I'm making minute adjustments to granular options like gyro sensitivity.
Potential Solution 1:
I'd like an option to for blank buttons to fall back to the bindings on my Default Profile. Anytime I update that button in Default, it should be reflected across all other profiles with blank bindings.
This would also be great for shift layers. They should fall back to the bindings of the main layer until individually overridden.
This should also be paired with a new "None" binding option, for when a user wants a button to stay blank without falling back to the Default profile.
Potential Solution 2:
Create a new "Inherit", "Fallback", or "Transparent" binding option, so that people can manually decide which buttons they want to enable fallback for.
Example 1:
Let's say that, in my Default profile, A is Enter and B is Escape.
If I make a New profile and leave A and B unbound, they should become Enter and Escape.
But if I ever decide to change my Default profile so that A is Escape and B is Enter, then my New profile should also update to match that.
Example 2:
Let's say that, in my Desktop profile, I have two buttons bound to Ctrl+Z and Ctrl+Shift+Z. They're universally accepted as Undo and Redo on most apps. However, Excel has a different binding for Undo: Ctrl+Y.
The default behavioral expectation is to copy my Desktop profile — along with all of its bindings — and rebind the button for Undo to Ctrl+Y.
But if I change anything in my Desktop profile
Extra:
These solutions would go very well with a "subprofile" system. Users could create a child profile for any other profile, then instead of blank inputs inheriting the Default Profile's bindings, they'd inherit their parent profile's bindings instead.
I have profiles for multiple games and apps, and they're usually lightly modified copies of my Default profile, with one or two bindings changed.
However, whenever I make a change to an input my Default profile, I then have to redo that change across ALL of my other profiles where I intend for that input to be identical. That can get pretty tiresome, especially if I'm making minute adjustments to granular options like gyro sensitivity.
Potential Solution 1:
I'd like an option to for blank buttons to fall back to the bindings on my Default Profile. Anytime I update that button in Default, it should be reflected across all other profiles with blank bindings.
This would also be great for shift layers. They should fall back to the bindings of the main layer until individually overridden.
This should also be paired with a new "None" binding option, for when a user wants a button to stay blank without falling back to the Default profile.
Potential Solution 2:
Create a new "Inherit", "Fallback", or "Transparent" binding option, so that people can manually decide which buttons they want to enable fallback for.
Example 1:
Let's say that, in my Default profile, A is Enter and B is Escape.
If I make a New profile and leave A and B unbound, they should become Enter and Escape.
But if I ever decide to change my Default profile so that A is Escape and B is Enter, then my New profile should also update to match that.
Example 2:
Let's say that, in my Desktop profile, I have two buttons bound to Ctrl+Z and Ctrl+Shift+Z. They're universally accepted as Undo and Redo on most apps. However, Excel has a different binding for Undo: Ctrl+Y.
The default behavioral expectation is to copy my Desktop profile — along with all of its bindings — and rebind the button for Undo to Ctrl+Y.
But if I change anything in my Desktop profile
Extra:
These solutions would go very well with a "subprofile" system. Users could create a child profile for any other profile, then instead of blank inputs inheriting the Default Profile's bindings, they'd inherit their parent profile's bindings instead.
Comment