You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a HotkeySystem starts out with the default bindings, and then set_config is used to replace those with new bindings, it behaves badly when one of those new bindings conflicts with one of the old bindings.
When it goes to set Undo to Numpad 4, it still sets that in the config, but then signals a failure that leaves the old bindings from Skip onward in place to result in
If a
HotkeySystem
starts out with the default bindings, and thenset_config
is used to replace those with new bindings, it behaves badly when one of those new bindings conflicts with one of the old bindings.Old bindings:
New bindings:
When it goes to set
Undo
toNumpad 4
, it still sets that in the config, but then signals a failure that leaves the old bindings fromSkip
onward in place to result inBadly-merged bindings:
With a conflict between
Undo
andPrevCmp
staying in the config because it didn't go on to setPrevCmp
to None.My desired behavior would be to un-register the conflicting
PrevCmp
binding before it registers the newUndo
binding asNumpad 4
.The text was updated successfully, but these errors were encountered: