Hi Sandy, this not a bug in MITK.
As Matt mentioned in his reply, he introduced a new feature in our fork. The cause of the misunderstanding was that I did not know about this, and I tested our application with the MITK upstream, not with our fork. For our segmentation tool we need to see the seeds only from the current slice. In MITK you see also points from the slice behind the current one. (If the cross is bigger than the slice distance.) In our fork this can be controlled by a data node property. I think, this is a useful feature, so it might be worth considering merging it to the MITK master. See Matt's email below. Regards, Miklos ------------------------------------------------------ In the NifTK fork, we explicitly turned that behaviour off using a property. :-) See here: https://github.com/NifTK/MITK/commit/6dc50f81de6ad7b9c3344554d0a4dc53867112f9 and http://bugs.mitk.org/show_bug.cgi?id=12003 so, from our point of view …. the question might be… Does bug 12003 need merging to MITK master? Does anyone else want it? ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
