# Include functionality of control point status in custom scripted module

**URL:** <https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658>\
**Category:** Development\
**Tags:** markups-fiducials, markups\
**Created:** [January 2, 2026, 9:42am UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658 "2026-01-02T09:42:14Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![W.J.Heerink](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/w.j.heerink/32/4894_2.png) [@W.J.Heerink](https://discourse.slicer.org/u/W.J.Heerink)\
**Post date:** [January 2, 2026, 9:42am UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/1 "2026-01-02T09:42:14Z")

</div>

Hi, I really like the use of the control point status as it is implemented in the Markups module. I mainly use the functionality of the buttons in the column of the table to change the status of individual control points.

Currently, I am building a scripted module where I would like to implement the same functionality, because the constant switching between the custom scripted module and the Markups module would be annoying.

To my knowledge, qSlicerSimpleMarkupsWidget does not provide this functionality. Is there an easy way to get the same kind of table integrated in my module?

Thanks!

---

<div class="post-metadata">

**Author:** ![W.J.Heerink](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/w.j.heerink/32/4894_2.png) [@W.J.Heerink](https://discourse.slicer.org/u/W.J.Heerink)\
**Post date:** [January 8, 2026, 8:46pm UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/2 "2026-01-08T20:46:24Z")

</div>

I found this issue in the attic that seems to be related: [Add reusable widget for markups control point list · Issue #6452 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/6452)

@lassoan Do you think there will be progress on this feature anytime soon? Thanks!

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [January 8, 2026, 8:52pm UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/3 "2026-01-08T20:52:43Z")

</div>

It would be easy to add a “position status” column to the simple markups widget, which you could click to cycle through the position states (as in the main Markups GUI). Would that be sufficient for your use case?

---

<div class="post-metadata">

**Author:** ![W.J.Heerink](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/w.j.heerink/32/4894_2.png) [@W.J.Heerink](https://discourse.slicer.org/u/W.J.Heerink)\
**Post date:** [January 8, 2026, 9:42pm UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/4 "2026-01-08T21:42:09Z")

</div>

Yes it would. As I mainly need to toggle control points between missing and defined as well as put them in place mode to define undefined points.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [January 10, 2026, 6:06pm UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/5 "2026-01-10T18:06:40Z")

</div>

I’ve added this new feature, it is currently under review.

> <https://github.com/Slicer/Slicer/pull/8955>
>
> The new column is hidden by default. Its visibility is controlled by the positio…nStatusColumnVisible property.
> 
> Requested in https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658
> 
> related to #6452
> 
> Example:
> 
> \`\`\`
> w=slicer.qSlicerSimpleMarkupsWidget()
> w.setMRMLScene(slicer.mrmlScene)
> w.setPositionStatusColumnVisible(True)
> w.show()
> \`\`\`
> 
> \<img width="742" height="219" alt="image" src="https://github.com/user-attachments/assets/fe97a3c4-f2e6-4335-b275-22901aa2dd70" /\>

---

<div class="post-metadata">

**Author:** ![W.J.Heerink](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/w.j.heerink/32/4894_2.png) [@W.J.Heerink](https://discourse.slicer.org/u/W.J.Heerink)\
**Post date:** [January 12, 2026, 11:18am UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/6 "2026-01-12T11:18:17Z")

</div>

Thank you so much for quickly resolving this request. I guess it will be available in the new nightly release? Is there any way to get it working within a stable release, too?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [January 12, 2026, 4:34pm UTC](https://discourse.slicer.org/t/include-functionality-of-control-point-status-in-custom-scripted-module/45658/7 "2026-01-12T16:34:08Z")

</div>

It was merged two days ago, so it should be already available in the latest Slicer Preview Release.

We usually don’t backport new features into patch releases, so it will be available in the new Slicer Stable Release (5.12) in about 3 month.