Summary of problem description

actual behaviour

• PointContainer and PointDataContainer members of mitk::PointSet get asynchronous

expected behaviour

• PointContainer and PointDataContainer should contain the same PointIDs

Cause of the bug

(How could this happen?, what went wrong?)

• faulty implementation of ExecuteOperation() in mitk::PointSet

Proposed solution

• Apply all instert/remove operations to both PointContainer and PointDataContainer.

Affected classes

* mitk::PointSet

How will the bugfix get tested?

• I found this bug while improving the unit test. Therefore a testcase for this bug already exists (see attachment to this bug).