NavigationPane does not show all connection when the RadDiagram IsVirtualized
The settings pane doesn't take into account the scenario when its popup is opened close to the top or bottom bounds of the screen, in the calculation of its vertical position. Available in R2 2016 SP
The PrintSettingsViewModel ' s MergeAndValidatePrintTicket method might throw PrintQueueExceptions. Catch them and provide info to the users somehow, for example args in the PreviewPrint event.
DragAndDrop from toolbox is not working if an external dll is located in the GAC and the DiagramToolBox is located there.
If you pan the Diagram on touch device the Pan event is not fired. Available in R3 2016 Release
Shape is dropped onto ContainerShape and the container is auto-resized. When you press Ctrl + Z, the shape is removed, but the old size of the Container is not reverted. Expected : the container should return to its old size. When there is a nesting of containers and you drop a shape into in innermost container, Ctrl + Z will return the previos size of the container. Available in R3 2016 Official Release.
When you start resize operation on a grouped ContainerShape and Shape in it the Container shape size can not be shrink-ed more than the previous BottomRight position of the shape in it (despite that the shape size is changed and there is space for the collapsing). Available in LIB version: 2016.1.21
If we have a custom shape that derives from RadDiagramShapeBase and we rotate it at some degree (90) for example, and then resize it the diagram's selection adorner is misplaced with the shape. Workaround:
Set RenderTransofrmOrigin = new Point(0.5, 0.5) to the shape.
Other workaround: Derive the custom shape from RadDiagramShape, instead of RadDiagramShapeBase.
A possible workaround is to use an attached property. Basically, we've added ConnectionPointsProperty in AttachedProperties class and added binding to this new property in the style of the connection. public class AttachedProperties { public static RadDiagram Diagram { get; set; } public static readonly DependencyProperty ConnectionPointsProperty = DependencyProperty.RegisterAttached("ConnectionPoints", typeof(List<Point>), typeof(AttachedProperties), new PropertyMetadata(null, OnConnectionPointsChanged)); public static IEnumerable<Point> GetConnectionPoints(DependencyObject obj) { return (IEnumerable<Point>)obj.GetValue(ConnectionPointsProperty); } public static void SetConnectionPoints(DependencyObject obj, IEnumerable<Point> value) { obj.SetValue(ConnectionPointsProperty, value); } private static void OnConnectionPointsChanged(DependencyObject d, DependencyPropertyChangedEventArgs e) { var connection = d as RadDiagramConnection; var connectionPoints = e.NewValue as List<Point>; if (connection != null && connectionPoints != null) { for (int i = 0; i < connectionPoints.ToList().Count; i++) { connection.ConnectionPoints.Add(connectionPoints.ToList()[i]); } connection.IsModified = true; (connection as IConnection).Update(); } } } <telerik:RadDiagram.ConnectionStyle> <Style TargetType="telerik:RadDiagramConnection"> <Setter Property="ConnectionType" Value="Polyline"/> <Setter Property="local:AttachedProperties.ConnectionPoints" Value="{Binding MyConnectionPoints}"/> </Style> </telerik:RadDiagram.ConnectionStyle>
The RadDiagramContainerShape class is quite limited as a container because it has a header, resizes to fit the content and has fixed padding around the borders for the children. A simple base RadDiagramContainerShape that doesn't have a default style and doesn't impose any layout constraints on the children will be very useful to create custom containers to build nested shapes for UI design tools. Thanks Reason for Closing: Changing the class the RadDiagramContainerShape inherits from will be a breaking change we cannot afford. The mentioned customizations are possible via inheritance and custom styles.
A stackOverflow exception is thrown when the diagram is layouted with AStarRouter, Sugiyama and connection bridges. Available in LIB version: 2015.3.1026
Diagram has no ContainerShapes. Layout returns different results when TreeLayoutSettings.IgnoreContainers is True / False. Same issue is produced when layout is sugiyama and sugiyamasettings' IgnoreContainers is True When True, the result is incorrect - every shape is treated like separate graph component. The fix is available in LIB Version 2015.1.0420.
ContainerShapes has connections connecting shapes in it. RouteConnections is True. After Expand Collapse - the ContainerShape has wrong size. The bug is introduced in Q1 2015. Available in LIB version: 2015.1.1603
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.
Using TreeLayout may lead to a memory leak because the TreeLayoutProcessor keeps a reference to the layout Root. Available in LIB version: 2014.3.1402
OrgTreeRouter holds references to RadDiagramConnections which are not removed from memory. Available in LIB version: 2014.3.1409
IsPanEnabled property is not respected when the diagram is panned with touch/pan gesture Available in LIB version: 2014.3.1409
If you manually remove a connection from a container (Source and Target are still in the container) and then drag this container in another one an exception will be thrown. The fix is available in LIB Version 2014.3.1326.
At the moment the ItemSnaping works only with the outer bounds but it should also snap to the centers.
When using SettingsPane on connection, the source and target cap types combos can be misaligned. For example when source is None and target is arrow 1. Available in LIB version: 2014.3.1319