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
I tried to do a skeleton annotation in the YZ viewport. Instead of placing nodes with my left click, wK selected (=made active) the closest node. Likely the node selection radius algorithm is not considering a the anisotropy of YZ plane?
In the video below you see me 1) move in X direction for a few slices 2) try to place a node with left click and 3) jump back to last/previous node position because it got selected instead of putting a new node.
node.placement.bug.mp4
Expected Behavior
Left click in YZ should create a node even when close to existing nodes.
Current Behavior
Left click in YZ selects a closeby node.
Steps to Reproduce the bug
In a skeleton annotation, in the YZ view
Move in X direction for a few slices
try to place a node with left click and
jump back to last/previous node position because it got selected instead of putting a new node.
Your Environment for bug
Browser name and version: Chrome
Operating System and version: MacOS
Version of WebKnossos (Release or Commit): 15095
The text was updated successfully, but these errors were encountered:
Context
I tried to do a skeleton annotation in the YZ viewport. Instead of placing nodes with my left click, wK selected (=made active) the closest node. Likely the node selection radius algorithm is not considering a the anisotropy of YZ plane?
In the video below you see me 1) move in X direction for a few slices 2) try to place a node with left click and 3) jump back to last/previous node position because it got selected instead of putting a new node.
node.placement.bug.mp4
Expected Behavior
Left click in YZ should create a node even when close to existing nodes.
Current Behavior
Left click in YZ selects a closeby node.
Steps to Reproduce the bug
In a skeleton annotation, in the YZ view
Your Environment for bug
The text was updated successfully, but these errors were encountered: