# Markups nodes: enabling measurements may propagate on newer nodes

**URL:** <https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269>\
**Category:** Support\
**Created:** [June 7, 2026, 11:45am UTC](https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269 "2026-06-07T11:45:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [June 7, 2026, 11:45am UTC](https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269/1 "2026-06-07T11:45:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [June 7, 2026, 3:45pm UTC](https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269/2 "2026-06-07T15:45:48Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [June 7, 2026, 4:56pm UTC](https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269/3 "2026-06-07T16:56:18Z")

</div>

> [@muratmaga](#):
>
> I can reproduce on this MacOS with slight variations.

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.

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [June 7, 2026, 6:49pm UTC](https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269/4 "2026-06-07T18:49:40Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [June 7, 2026, 7:24pm UTC](https://discourse.slicer.org/t/markups-nodes-enabling-measurements-may-propagate-on-newer-nodes/47269/5 "2026-06-07T19:24:12Z")

</div>

Yep, done [here](https://github.com/Slicer/Slicer/issues/9214).