Hi Marco,
I opened a ticket for this issue and pushed a branch with a unit test.
http://bugs.mitk.org/show_bug.cgi?id=17295
https://github.com/NifTK/MITK/compare/bug-17295-atomic-state-transitions
It would be really good to eliminate the superfluous signals from the Core
and write state consistency checks. I noticed a few strange things, e.g.
sometimes I get different results if I set a 3D world position to the SNCs
by SelectSliceByPoint() and then get their slice index by
GetSlice()->GetPos(), or if I transform the position to discrete indexes by
the WorldToIndex function of the geometry. I am not 100% sure at the moment
if this is an MITK bug or it's in our viewer, but such consistency tests
would definitely be required, and it is pretty straightforward to express
them with this little test suite.
Cheers,
Miklos
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
