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
When rebinding a keyboard key to a new key, with a different action, the old binding can be removed, or can be left depending on ordering issues in the binding. As well, two keys cannot be bound to the same action.
It is ordering dependent, if you assign an existing assigned key to a new function, for example
{ commandName: 'rotateViewportCW', label: 'Rotate Right', keys: ['r'] },
{ commandName: 'invertViewport, label: 'Rotate Right', keys: ['r'] },
{ commandName: 'rotateViewportCW', label: 'Rotate Right', keys: ['right'] },
then the ordering will delete one of the commands.
Describe the Bug
When rebinding a keyboard key to a new key, with a different action, the old binding can be removed, or can be left depending on ordering issues in the binding. As well, two keys cannot be bound to the same action.
Steps to Reproduce
Rebind the pageup key with:
{
commandName: 'incrementActiveViewport',
label: 'Next Image Viewport',
keys: 'pageup',
isEditable: true,
},
added as a new binding. This may or may not take affect depending on the keyboard binding setup.
The expected behaviour is that the pageup key binding gets replaced with the new command.
The current behavior
The binding may or may not occur depending on ordering
The expected behavior
The new binding should be updated correctly, and should allow binding to multiple keys.
OS
Windows 11
Node version
NA
Browser
Chrome
The text was updated successfully, but these errors were encountered: