The mitk::DisplayPositionEvent can be initialised by a display position, and the world position is calculated at the first request. However, if the display position is changed through a setter, the world position is not recalculated.
Description
Event Timeline
I noticed the same error in mitk::KeyEvent. It would be worth checking the other event types, too.
Any update on this?
I want to update our fork after the new MITK release and want to revert our patches that have already be merged to the upstream master, so that we can be as close to the upstream as possible.
We test the patch on the three main platforms, with no problem.
[ee6357]: Merge branch 'bug-16409-InconsistentDisplayPosition-Int'
Merged commits:
2014-03-05 15:18:12 Christian Weber [dac416]
Remove wrong member from being set,
2014-03-05 15:00:07 Christian Weber [1bad57]
Merge branch 'bug-16409-InconsistentDisplayPosition' into bug-16409-InconsistentDisplayPosition-Int
2014-03-05 14:59:14 Christian Weber [033ceb]
Adapt KeyEvent as well
2014-03-05 14:58:22 Christian Weber [1a41d3]
Display event world position recalculated if display position changed
Signed-off-by: Miklos Espal <'m.espak@ucl.ac.uk'>