# SlicerQR Development

**URL:** <https://discourse.slicer.org/t/slicerqr-development/15954>\
**Category:** Development\
**Tags:** registration, build, segmentation, dicom, python\
**Created:** [February 11, 2021, 3:59pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954 "2021-02-11T15:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 134

<div class="post-metadata">

**Author:** ![spycolyf](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@spycolyf](https://discourse.slicer.org/u/spycolyf)\
**Post date:** [April 16, 2021, 6:29pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954/134 "2021-04-16T18:29:31Z")

</div>

> [@mau\_igna\_06](#):
>
> vtkMRMLMarkupsLineNode

Some info is here I believe. In case you want to know.

> [@Help with orientation marker and ruler](https://discourse.slicer.org/t/help-with-orientation-marker-and-ruler/13454/4):
>
> Hello again, I spoke to the people who will be the end users of my Slicer module and they really do want something more precise than the built-in ruler tool I referred to in the first post in this thread. If you have any links to share that could help me figure out the syntax for adding a ruler tool to my module (using qSlicerSimpleMarkupsWidget?) that would be greatly appreciated.

---

_[View the full topic](https://discourse.slicer.org/t/slicerqr-development/15954)._