I stumbled upon mitk::LevelWindow while working on scene serialization.
mitk::LevelWindow seems to mix concepts of level/window and min/max. At least these are mixed within the member variable naming.
- Go through the code and decide on one concept.
- Either store current and default values as level/window or as min/max pair. (I vote for level/window, since this is more generally known, I guess)
- name the Get...() methods consistent
- document the used concepts in the class documentation. A small diagram would help much.