Fix loss of control if A becomes unmapped #65
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a feature is updated, it might conflict with an existing feature. Instead of erasing the existing feature, an attempt is made to update its primitives to the old feature being overwritten. For example, if the button map is: A -> 0 B -> 1 And the user maps "B -> 0", then the new button map will look like: A -> 1 B -> 0 Here, instead of erasing the A (button 0) when it conflicts with the new B (also button 0), the A is updated to point to B's old button (1).
|
Looks good to me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a feature is updated, it might conflict with an existing feature. Instead of erasing the existing feature, an attempt is made to update its primitives to the old feature being overwritten.
For example, if the button map is:
A -> 0
B -> 1
And the user maps "B -> 0", then the new button map will look like:
A -> 1
B -> 0
Here, instead of erasing the A (button 0) when it conflicts with the new B (also button 0), the A is updated to point to B's old button (1).
Part of xbmc/xbmc#10630