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 using the multiModifier selection type, once the modifier key has been pressed (and detected by the onKeyDown handler), there is no way to deselect nodes. It appears the problem is that there is no corresponding onKeyUp handler to detect when the modifier key is released.
Steps to Reproduce the Bug or Issue
Create a graph using mulitModifier selection mode
Press the modifier key and select a couple of nodes.
Release the modifier key.
Notice that the graph continues to behave as if the modifier key were pressed.
Click the canvas to clear the selection.
Notice that when clicking nodes the graph behaves (correctly) as if the modifier key were not pressed.
Expected behavior
After step 4 (in the step to reproduce the bug above), I expect to be able to deselect a selected node by clicking on it, or select a single node by clicking on a deselected node.
Screenshots or Videos
No response
Platform
Reagraph Version: 4.19.3
OS: macOS
Browser: Chrome, Safari
NodeJS version: v22.4.1
Your Example Website or App
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the
multiModifier
selection type, once the modifier key has been pressed (and detected by theonKeyDown
handler), there is no way to deselect nodes. It appears the problem is that there is no correspondingonKeyUp
handler to detect when the modifier key is released.Steps to Reproduce the Bug or Issue
mulitModifier
selection modeExpected behavior
After step 4 (in the step to reproduce the bug above), I expect to be able to deselect a selected node by clicking on it, or select a single node by clicking on a deselected node.
Screenshots or Videos
No response
Platform
Your Example Website or App
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: