# A few issues with the new Markups
**URL:** https://discourse.slicer.org/t/a-few-issues-with-the-new-markups/6051
**Category:** Development
**Tags:** markups
**Created:** [March 6, 2019, 10:24pm UTC](https://discourse.slicer.org/t/a-few-issues-with-the-new-markups/6051 "2019-03-06T22:24:33Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@smrolfe](https://discourse.slicer.org/u/smrolfe)
#### Post date: [March 6, 2019, 10:24pm UTC](https://discourse.slicer.org/t/a-few-issues-with-the-new-markups/6051/1 "2019-03-06T22:24:33Z")
I’ve been using the new Markups module and have run into a few issues. I’m testing on the most recent nightly build.
1. Toggling the visibility of landmarks causes them to be permanently invisible.
2. The 2D projection option does not appear to be working.
3. The GetMarkupPoint() function in vtkMRMLMarkupsFiducialNode does not appear to be supported. Is this planned? I believe I can also use GetMarkupPointVector() to do the same thing.
---
### Author:  [@smrolfe](https://discourse.slicer.org/u/smrolfe)
#### Post date: [March 6, 2019, 10:31pm UTC](https://discourse.slicer.org/t/a-few-issues-with-the-new-markups/6051/2 "2019-03-06T22:31:40Z")
2D projection is not yet implemented, as noted in this thread:
> [@Adding points to open curve](https://discourse.slicer.org/t/adding-points-to-open-curve/6044/5):
>
> thanks for reporting. Fiducial projection is still not implemented. For reference here there are all the known reaming bugs and missing features: [https://1drv.ms/x/s!Arm\_AFxB9yqHtvxAsyBDU\_3C1IxfGA](https://1drv.ms/x/s!Arm_AFxB9yqHtvxAsyBDU_3C1IxfGA)
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [March 7, 2019, 12:03am UTC](https://discourse.slicer.org/t/a-few-issues-with-the-new-markups/6051/3 "2019-03-07T00:03:25Z")
> [@smrolfe](#):
>
> Toggling the visibility of landmarks causes them to be permanently invisible.
Added an issue to the spreadsheet.
> [@smrolfe](#):
>
> The GetMarkupPoint() function in vtkMRMLMarkupsFiducialNode does not appear to be supported. Is this planned? I believe I can also use GetMarkupPointVector() to do the same thing
`GetNthControlPointPosition` method should be used instead. I’ll add a method (marking it as deprecated) to make transition to the updated API easier. The API was really messy, using “vector” and “world” suffixes and data types quite inconsistently. It is still not very clear, so we’ll improve it further (but keep old methods in place for a while).
---
### Author:  [@smrolfe](https://discourse.slicer.org/u/smrolfe)
#### Post date: [March 7, 2019, 2:29am UTC](https://discourse.slicer.org/t/a-few-issues-with-the-new-markups/6051/4 "2019-03-07T02:29:48Z")
Great, thanks @lassoan!