Hi Matt,
I believe that this is meant for better usability. The crosses are rendered
smaller, to illustrate that a point is coming on a slice near to the current
one. Thus, the points are easier to locate and there should not be much
confusion about them, since they look different compared to "real" points.
Can you explain your use case? When is it mandatory for you to render the
points only and their exact location and no helper objects around to locate
them?
We have a plan to re-write this mapper and port all GL code to VTK. I guess
this would change the look a little and could even result in your desired
behavior. But I think we would like to keep this effect for usability purposes
and, in addition, we currently have no resources for this project.
Regards
Thomas
From: Clarkson, Matt [mailto:[email protected]]
Sent: Donnerstag, 17. Mai 2012 18:35
To: mitk-users
Subject: [mitk-users] Point Set Rendering in 2D
Hi there,
when points are rendered as crosses in 2D, they are also shown on previous and
next slices, but a bit smaller.
I believe that in mitkPointSetGLMapper2D.cpp this is caused by:
Vector3D diff=p-projected_p;
ScalarType scalardiff = diff.GetSquaredNorm();
and
if((m_ShowPoints) && (scalardiff<4.0))
{
I would like to have crosses only visible on the slice to which they correspond.
How would people suggest modifying this? An extra property to control whether
we draw them on prior/next slices? Or something else?
Thanks
Matt
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
