ROI selection tool broken in Slicer-4.13.0-2021-09-23 preview

We use ROI selection tool for selecting bounding box for scribbles method. It worked great in previous versions of Slicer (e.g. from two days ago in Slicer-4.13.0-2021-09-21 it worked fine).

With the latest preview release (Slicer-4.13.0-2021-09-23), there seems to be two issues:

1. The ROI tool has been significantly changed. It is now under markup module I believe where I am having a difficult time initialising and marking up an vtkMRMLAnnotationROINode node (see screenshot of before and after update). It would be good to have some guidance/documentation on how we can do the same interaction that we did in the version from two days ago. If this already exists, can you please point me to it.
2. The markup module crashes Slicer as soon as I click on ROI symbol from within the tool (see screenshot below) In the terminal from where I run Slicer, it gives the following error messages:

Switch to module: “MONAILabel” Switch to module: “Markups” GetItemByDataNode: Invalid data node to find GetItemByDataNode: Invalid data node to find error: [/home/user/Downloads/Slicer-4.13.0-2021-09-23-linux-amd64/bin/SlicerApp-real] exit abnormally - Report the problem.

Screenshots

Before the update (version Slicer-4.13.0-2021-09-21 )

After the update (version Slicer-4.13.0-2021-09-23)

cc: @lassoan

[lassoan]

I’ve pushed a fix (just minutes before the nightly build cutoff time). This should fix the problem of the place widget not changing the active markup node. Please test and let me know if there is any problem.

Also let us know if have any request for changing/improving markups ROIs. For example, the markups ROI is placed by clicking in two corners (instead of clicking the center and a corner as it was done in annotation ROIs). There is another mode that creates the ROI as the bounding box of control points. We can add the center+corner click mode if someone strongly prefers that.

[lassoan]

I was able to reproduce the sticky place button issue. Until the problem is fixed, a workaround is to use the toolbar to switch between active markup nodes. A fix should come soon.