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
What's the problem this feature will solve?
Right now if one wants to expand or shrink the area between nodes, both nodes have to be adjusted individually or more nodes need to be added in between.
Describe the solution you'd like
When you select the line between nodes, that segment turns red. This portion can be dragged and placed where desired (moves the nodes in tandem). This would also prevent whole polygons from moving when one accidentally selects a line and drags it (how it works now)
Innumerable ways this would help in the course of drawing, and a generally expected feature of many drawing tools (ITK-SNAP, for example)
Alternative Solutions
Just have to add more nodes or move more nodes, adding to ergonomic issues (and UX frustration)
LOW PRIORITY
The text was updated successfully, but these errors were encountered:
The handles allow to rotate or translate the annotation.
See #141 and #118
List of Slicer changes:
$ git shortlog e030103a5a..de0cffa95b --no-merges
Jean-Christophe Fillion-Robin (2):
[backport PR-5182] BUG: Ensure Slicer VTKWidget classes are available in python.
ENH: Support hiding interaction handles for specific markups representation
What's the problem this feature will solve?
Right now if one wants to expand or shrink the area between nodes, both nodes have to be adjusted individually or more nodes need to be added in between.
Describe the solution you'd like
When you select the line between nodes, that segment turns red. This portion can be dragged and placed where desired (moves the nodes in tandem). This would also prevent whole polygons from moving when one accidentally selects a line and drags it (how it works now)
Innumerable ways this would help in the course of drawing, and a generally expected feature of many drawing tools (ITK-SNAP, for example)
Alternative Solutions
Just have to add more nodes or move more nodes, adding to ergonomic issues (and UX frustration)
LOW PRIORITY
The text was updated successfully, but these errors were encountered: