Operating system: Mac OS 15.6.1 (24G90)
Slicer version: 5.10.0
Expected behavior: Don’t draw just because cursor is moving
Actual behavior: Draws unwanted areas, killing other segments
I finally got nnInteractive to help segment. The problem I’m having is one that I experienced when trying to segment by hand as well, but the consequences are more disastrous using the nninteractive module. It looks like Slicer thinks I’m trying to draw, but the mouse is released and I’m just trying to move the cursor somewhere else. What can I do to stop this behavior?
I just tested Slicer 5.10.0 on a mac book air with OS 15.6.1 and had no problem with the paint tool. I was using the built in track pad. I can’t explain why this wouldn’t work for you.
For nnInteractive, you can often use points or closed curves and get good results while you are investigating what why paint isn’t working for you.
I have occasionally run into this as well. It behaves as if the mouse button-up event got missed while the processor was busy. Doing another click has sometimes allowed Slicer to catch that event and get out of the dragging mode. Then, whatever was caused just needs to be undone. Since undo on painting works well, even with nnInteractive, I have found this annoying, but not fatal as long as it is not too frequent. My impression is that the closer you are to working at the limits of the machine’s memory/processing capabilities, the more likely this is to happen.