Andras Lasso

Thanks a lot, this looks very promising! 1. The main issue is that you added only a single vtkLineSource for an entire markup node. Since one markup node can display...

Thanks for the update, it looks good oks great! In the final solution we'll need something more controllable than the first master volume bounds. For example, we could use the...

Thanks a lot, I'll test this! What's the motivation for using a different color for line than for the text and glyph? (if there is a good reason to use...

> maybe I did not see the most obvious way to do that but (2) viewer attention is a bit "drawn" to the glyphs when using different colors like: OK,...

I'm building it now. Will test it and review the code today.

Thank you, this will be awesome. This is all quite hard, complex development tasks, so what you've done is really impressive. There are a number of things to fix/improve: -...

If you got stuck with your branch then you can check out the Slicer:master branch and cherry-pick your only commit (skip the merge commits). You can then force-push this new...

@rbumm I've rebased your branch on the latest Slicer master and force-pushed to your fork. You can check out your rbumm:Branch_markuplabeltexts branch and it should build without problems.

> I need a robust, preferable fast method that can be called from tkSlicerMarkupsWidgetRepresentation2D::UpdateAllPointsAndLabelsFromMRML to determine the sliceCenterRAS position I think you can get the slice center's RAS position by...

@jcfr do we know how the Slicer download site will work? It would be quite easy to implement this, but it does not make sense to implement it for the...