Syncfusion.Diagram.Windows

Syncfusion.Diagram.Windows Assembly

Namespaces
NamespaceDescription
 
Implements a generic diagram controller containing a default set of tools. The DiagramController class implements a concrete controller with a generic diagramming user interface. It overrides the initialize method and registers all available tools in the Diagram Windows assembly. A tool is an object that implements a distinct functionality for the controller. Tools can be added to the controller using the register tool method in order to customize the behavior of the controller.The DiagramController is responsible for coordinating the activation and deactivation of tools.Tools can be accessed by name with the GetTool method.It provide control to many tools such as move tool used to move any kind of object in the diagram, select tool to select an object, resizing tool, pan tool, insert node tool for inserting node in diagram. Zoom control is responsible for percentage of zooming of diagram. Line based tool to draw connectors between nodes, it also provides conrol to draw curved lines and connectors in the diagram. Connection point tool, each node can have a connection to connect from one node to another node This provides control to edit text and label in three ways InPlaceEditor, TextEditor, RichTextEditor. InPlaceEditor used to edit text in nodes. TextEditor and RichTextEditor are used to edit text in textboxes. This provides an additional control DiagramViewerEventSink control which inherits from ViewerEventSink and contains additional tool events handles. The DiagramController captures all mouse events and performs hit testing on the diagram. Nodes, ports, and vertices hit by mouse movements are tracked by the controller. Tools can access this hit testing information in the controller. In other words, the controller provides basic hit testing services to tools so that each tool doesn't need to implement (and possible duplicate) that hit testing logic. The DiagramController makes all focus to the related action through FocusManager control.
Interactive two-dimensional graphics control for diagramming, technical drawing, visualization, simulation, and technical drawing applications. This control provides a surface for rendering and manipulating 2D shapes, symbols, text, and images. The user interface supports drag- and-drop, scaling, rotation, zooming, grouping, ungrouping, connection points, and many other features. Activating user-interface tools is a task commonly performed by applications using this control. A diagram is composed of three objects: the Model, View, Controller. The model-view-controller architecture provides a clear separation between data, visualization, and user interface. The model contains the data portion of the diagram, the view is responsible for rendering the diagram, and the controller handles user interaction. The model, view, and controller are accessible as properties in this control and can be manipulated directly. Some of the methods and properties in this class are just wrappers that call identical methods in the model, view, or controller. For example, the following two lines of codes are equivalent: 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.