Display.CurrentTool property

Mar 18, 2013 at 12:37 PM
Edited Mar 18, 2013 at 12:37 PM
Why CurrentTool property is a member of the Display type and not a member of some UI-platform-independent interface? This pushes me to reference the WinformsUI assembly when I want to write smth. like this:
IDiagramPresenter diagramPresenter;
diagramPresenter = ...;
...
var currentTool = (diagramPresenter as Display).CurrentTool; // Display type lives in WinformsUI assembly
...
It would be nice to see CurrentTool property as member of some "core" interface (e.g. IDiagramPresenter).

Or... a "current tool" can exist only under WinForms?!
Coordinator
Mar 20, 2013 at 1:30 PM
I totally agree:
You should not be forced to reference WinForms in a UI-independent assembly.
I will add this point to our "Points To Discuss" list.