Accidentally moving all markups in a pointList

This was happening before but I though it was fixed. I can replicate this on MacOS 5.12.1 middle click and drag, moves the entire pointList. interaction is not enabled, so I would consider this a bug.

I always considered that as an interesting feature. Undo/Redo cancels the displacement nicely.

How do you determine this? Through context-menu or from Markups module? It appears the context menu interaction checkable item refers to interaction handle visibility and is different from the Interaction locked state of the Control Points.

Where is the undo? I am not aware of it. Is it finally done?

No that interaction lock is not set. I do need to be able to interact with the individual points. I refer to the interaction widget which is specifically for this kind of rotation/translation movement.

Moving an entire Markups node by mouse wheel click has been a feature for a while. The way to prevent translation block of the control points would be with the control point locked state being set.

But it is a dangerous operation without a reliable undo operation. We can’t translate model or volume like that. Why is that enabled for markups?

It is particularly concerning and confusing, since middle button and drag has indeed a specific function to drag the camera. But if this hits a markup this moves it without anyway to undo.

It’s not in Slicer core, I am using an external module for that. It has been working seamlessly the few times I needed that.

Yes, that’s the one also available in SlicerMorph. But it is not in the core and has to be enabled manually.

This is not a plea for myself. A lot of people use pointLists to do manual anatomical landmarks on 3D data whether clinical or biological. It is extremely frustrating to accidentally mess up your data you spend 10 minutes creating by a simple mistake without the option of undo. We are modifying user data without consent, and in a destructive way, which none of the modules I am aware of does it in this way.

This is the kind of thing that makes Slicer frustrating.

I can’t think of one, but if there is a need for this use case, then this should be an option that can be easily turned off and on (without using interaction lock, which disables every kind of interaction, which is non-starter).