Diagram Shapes' property is bound to property from the ViewModel. Case 1) Using GraphSource =>Shapes DataContext is automatically apllied. GraphSource is set to null or changed. Or Case 2) Not using Graphsource. Shape's DataContext is set manually (in code behind). Diagram.Clear() is invoked. Result: Binding Expression erors in Output indicate missing properties - these are bound properties of the shapes.
Should be able to override the AbsolutePosition and the Offset of the connector. Should be able to specify absolute position manually, not only relative. Should be able to provide template for its visual representation. Fixed in LIB version: 2014.2.0914
There should be annotations (comments) system built into the framework: €¢something like Word where one can add to a word a note €¢something like Excel with its comments bag €¢something like Workflow Foundation where every shape has a popup bag
This is reproducible only if you set the RotationOrigin property to a value different than (0.5,0.5). Also, the rotation angle is wrong only on the first call of the Rotate() method of the service. To work this around you can create a custom RotationService and override its CalculateRotationAngle() method where you can calculate custom angle. http://docs.telerik.com/devtools/wpf/controls/raddiagram/features/services https://github.com/telerik/xaml-sdk/tree/master/Diagram/CustomServices
Connection Bridges Greatly Degrade Performance. Iven if there are no crossings, performance is very slow. In some scenarios empty spaces on the connections are observed even if there are no crossings. The fix will be available with Q1 2015 Release.
Add spell checking to the shape and connections, while editing
When a RadDiagramItem is deserialized, some of its properties receive local values. This is why if you have applied style setters on these properties, the value applied by the style setter is no longer used.
In some cases when there are no crossings, empty spaces can be observed on the connections. The fix will be available with Q1 2015 Release.
Select some color from settings pane for some shape. In order to use the same color for other shape you need to deselect this color on your own (by selecting other color) and then select it again. Available in LIB version: 2014.3.1117
Implemented functionality that detects a connection creation being cancelled through the Esc key and notifies the user In order to take advantage of this functionality you should inherit the ConnectionTool of RadDiagram and override the KeyDown method - if it returns true the tool action has been canceled. More about how to customize RadDiagram tools you can find in our help topic " Tools Customization": http://www.telerik.com/help/wpf/raddiagram-tools-customization.html Available in LIB version: 2014.3.1103
Windows DPI is 125 % (you need to sign out from win 10 then sign in again in order to apply the setting successfully). Diagram is hosted in RibbonWindow. The diagram ruler does not show the ticks and labels on the left of the zero tick (label). The Position property of Diagram could (0,0) or (500, 0), (300, 0) etc... Check the attached image for better illustration. Workaround could be replacing the RibbonWindow with MS Window.
A small glitch appears when the pencil tool is used. The glitch is demonstrated in the attached image.
When you switch between two different positions and zoom levels leads to a wrong visualization of the diagram items.
When you paste a big image (bigger than 1024px) it gets blurry
If you have two nested containers and a shape inside the inner container a wrong connector will be activated if you try to create connection (target) to the shape. This can be reproduced with the MVVM SDK example. Try to connect the "Polo" shape to the "Bugatti" shape. The auto connector of the "Bugatti" shape will not be activated when the endpoint of the connection is inside the shape. It will be activated only if you directly hover over the connector.
The AStar routing does not calculate the RouterInflation for shapes which are located in collapsed ContainerShape.
Using a custom router and gliding connectors may lead to a StackOverflow Exception. The exception is due to an endless update of the connection Start/End points and the ConnectionPoints. Resolution: The fix will be included in R2 2017 SP in June 2017. Generally, avoid using GlidingConnectors and custom Router which calculates intermediate points based on connections' StartPoint/EndPoint. This is а prerequisite of circular dependency between Start/EndPoint and ConnectionPoints. Gliding Connectors essence is to set StartEndPoints and sometimes they are based on the connection points' first and last point. On the other hand, custom router based on Start/EndPoint makes the opposite- connection points depend on start/end. Instead, the client can use the connection.Source.Bounds.Center (Top, Bottom, Left, Right etc) and connection.Target.Bounds.Center(Top, Bottom, Left, Right etc) in a custom router. Available in LIB version: 2017.2.515