# Markups Module Slicer 4.11.0
**URL:** https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234
**Category:** Development
**Created:** [November 20, 2019, 5:42pm UTC](https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234 "2019-11-20T17:42:57Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@rprueckl](https://discourse.slicer.org/u/rprueckl)
#### Post date: [November 20, 2019, 5:42pm UTC](https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234/1 "2019-11-20T17:42:57Z")
Hi,
currently, I don’t know really where to report bugs or feature requests, so I’m doing it here:
Slicer 4.11.0-2019-11-19:
**1:**
In the markups module, when I create a MarkupsLine, a 2D projection is always visible in one slice view, even when projection is turned off:
**2:**
When I disable the visibility of both control points of a MarkupsLine, the line should ideally stay visible in the 3d view, as it does in the slice view. Currently, it disappears from the 3d view:
**3:**
Ideally, the Glyph sizes for the control points and the lines in between (this applies for MarkupsLine, MarkupsAngle, MarkupsCurve, MarkupsClosedCurve) could be adjusted independently.
BTW: I find the new Markups Module very well designed!
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [November 20, 2019, 6:23pm UTC](https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234/2 "2019-11-20T18:23:00Z")
> [@rprueckl](#):
>
> In the markups module, when I create a MarkupsLine, a 2D projection is always visible in one slice view, even when projection is turned off:
Most likely it is not a projection but the line actually crosses that slice.
> [@rprueckl](#):
>
> When I disable the visibility of both control points of a MarkupsLine, the line should ideally stay visible in the 3d view, as it does in the slice view.
I agree, line visibility should be adjustable independently from point visibility.
> [@rprueckl](#):
>
> Glyph sizes for the control points and the lines in between (this applies for MarkupsLine, MarkupsAngle, MarkupsCurve, MarkupsClosedCurve) could be adjusted independently
I agree, this would be nice to have.
> [@rprueckl](#):
>
> currently, I don’t know really where to report bugs or feature requests
We are in the process of transitioning Slicer fully to github. Once that’s done (hopefully within days), we can start using GitHub’s issue tracker. Until then I use this [spreadsheet](https://1drv.ms/x/s!Arm_AFxB9yqHuOwEoD572qECck1T5w?e=MUBhgh) to track markups module developments.
Right now, as far as I know, all Slicer core developers have other priorities, so if you can implement any of the fixes or enhancements and send pull requests that would be great help.
---
### Author:  [@rprueckl](https://discourse.slicer.org/u/rprueckl)
#### Post date: [November 21, 2019, 9:27am UTC](https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234/3 "2019-11-21T09:27:56Z")
> [@lassoan](#):
>
> Most likely it is not a projection but the line actually crosses that slice.
The only difference when “2D Projection” is activated is, that the control points are shown throughout the slices. There is no difference for the display of the line itself. It is always shown with a fade and (as far as I have seen) there is no way to disable this. It would be really cool to have more control:
- fading rate (in number of slices (1-inf))
- e.g. dashed line display
- display the intersection point of the line with the current slice (e.g. select from available glyphs)
Currently, it is not really intuitive what the changes in color and transparency mean. A suggestion for clarification would be the following: Display the projected points with a small symbol indicating in which direction the point is located (in the example image L for left and R for right from the current slice, or arrows corresponding to the direction of the scrollbar of the slice view). A cross marks the intersection of the line with the current slice:
Another suggestion would be to vary the size of the projected points with the distance to them. This would probably give you a good feeling of distance during scrolling and whether you are scrolling towards or away from a specific point.
> [@lassoan](#):
>
> Right now, as far as I know, all Slicer core developers have other priorities, so if you can implement any of the fixes or enhancements and send pull requests that would be great help.
Currently, we are working on the first release of our software. For this, we use what is already there (4.10.2 release right now). Once we have established the initial set of functionality and released that one, we are planning to refine. In this stage, we will also make adaptations to the slicer code if necessary or helpful, which we will contribute.
I just want to deposit things that pop into my eyes now, so that it is somewhere noted on a list 🙂
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [November 21, 2019, 1:48pm UTC](https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234/4 "2019-11-21T13:48:35Z")
> [@rprueckl](#):
>
> The only difference when “2D Projection” is activated is, that the control points are shown throughout the slices.
Yes. Maybe 2D projection should be renamed to “Control point projection”. Or change the behavior to project lines to the slice the same way as points.
> [@rprueckl](#):
>
> Another suggestion would be to vary the size of the projected points with the distance to them.
Changing the size of the projected points or adding arrows are good ideas.
> [@rprueckl](#):
>
> A cross marks the intersection of the line with the current slice
I agree it would be often useful.
Of course it is not possible to implement all ideas (implementation, maintenance, and usability would suffer), but we can certainly selectively implement some of these.
> [@rprueckl](#):
>
> It would be really cool to have more control:
>
> - fading rate (in number of slices (1-inf))
You have full control over how color and opacity changes depending on signed distance from the slice: either using [SetLineColorFadingStart/End/Saturation/HueOffset…()](https://apidocs.slicer.org/master/classvtkMRMLMarkupsDisplayNode.html#a447cc0476faf08e18fb031a57bb361b4) methods (to still use a linear ramp but with custom fadeout properties) or by using [SetLineColorNodeID](https://apidocs.slicer.org/master/classvtkMRMLMarkupsDisplayNode.html#a09c3ed7c1e3307f1c7090f7102b98efb) (to use an arbitrary non-linear distance/color mapping).
> [@rprueckl](#):
>
> Currently, we are working on the first release of our software. For this, we use what is already there (4.10.2 release right now). Once we have established the initial set of functionality and released that one, we are planning to refine. In this stage, we will also make adaptations to the slicer code if necessary or helpful, which we will contribute.
Sounds good!
---
### Author:  [@rprueckl](https://discourse.slicer.org/u/rprueckl)
#### Post date: [November 26, 2019, 2:01pm UTC](https://discourse.slicer.org/t/markups-module-slicer-4-11-0/9234/5 "2019-11-26T14:01:45Z")
> [@lassoan](#):
>
> Of course it is not possible to implement all ideas (implementation, maintenance, and usability would suffer), but we can certainly selectively implement some of these.
Sure, I just want to provide input for discussions about possible features.