Markups nodes: enabling measurements may propagate on newer nodes

Support
1

I am seeing an unexpected behaviour regarding the display of measurements in markups nodes, in all versions of Slicer on Linux.

Start 5.10 stable for instance:

  • draw a Closed curve node: no measurement is displayed
  • go to the Markups module
  • enable length and area: the measurements are displayed
  • draw a new Closed curve node: the length and area measurements are displayed

This can be reproduced with other markups nodes also, Slicer native or from ExtraMarkups.

While trying to reproduce this by code, the result is very inconsistent, sometimes expected and sometimes unexpected.

It would be of interest if someone could try to reproduce that in any environment.

Thanks.

2

I can reproduce on this MacOS with slight variations. As you describe I create a closed curve and then enable some of the measurements (length, curve, curvature, curvature max) and then drew another curve

on 5.10.

Second curve displayed the length only.

on 5.11 from June 2nd

Second curve displayed all three measurements.

I agree this a bit confusing, since I always thought to be property of individual markup object as opposed to default on and off (and if it is a global on/off, then one can argue it is in the wrong place in the UI).

3

Thank you for your reply. At least I know it’s not only me.

Measurement display should be a private property of each node IMO, like the colour of the node and its name.

4

You may want to open an issue for this to be tracked on the gh.

5

Yep, done here.