diagram.Undo();
// Same as
diagram.Controller.Undo();
Methods that are simple wrappers are documented as such.
private void drawRectangle_Click(object sender, System.EventArgs e)
{
this.Diagram.ActivateTool("RectangleTool");
}
diagram.Undo();
Same as
diagram.Controller.Undo();
This control provides the converter(Diagram Document Converter) returns whether this converter can convert the object to the specified type, using the specified context.
Graphical objects can be added to a diagram in several ways. One way is
through drag-and-drop. Symbols can be dragged from a paletteGroup view onto the diagram. Objects can also be added from the clipboard using the paste().
method. Shapes can be drawn onto the diagram by activating one of several drawing tools such as the rectangle tool.
Objects can also be created programmatically and added to the diagram by calling the appendchid method.
Objects can be displayed and editied in the diagram through property editor control.
This provides a control(Overview Control) implements an overview window that provides a perspective view of the diagram model.The OverviewControl is initialized with a diagram model and a view, and upon display renders a view
of the diagram that is scaled to the control's bounds.The viewport's origin corresponds to the origin of the diagram's view and moving the viewport
will shift the view's origin by an equivalent extent.
This control provides an interactive platform print set up consists of header and footer features and page set up control provides options to modify the page height, width and orientation while printing the document
The History manager control is used to record the actions performed during diagramming.By calling the HistoryManager.Undo() method removes the command on the top of the undo stack and causes an undo
to occur. The HistoryManager.Redo() method will redo the last command that was removed from the undo stack. The
UndoCommand and RedoCommand methods are usually called in response to clicking Undo and Redo on the Edit menu.
One advantage of the model-view-controller architecture is that the parts are interchangeable . Models, views, and controllers can be swapped in and out independently.
For example, the user interface of the diagram can be completely replaced by swapping in a different controller implementation.
[Editor(typeof(PaletteOpener), typeof(System.Drawing.Design.UITypeEditor))]
Please refer to the DiagramBuilder sample to see the HeaderFooterDialog in use.
Please refer to the DiagramBuilder sample to see the PageBorderDialog in use.
Please refer to the DiagramBuilder sample to see the PrintSetupDialog in use.