yFiles WPF 2.0.1 Release Notes

yFiles WPF 2.0.1 is the newest bugfix and maintenance release available.

Technical Requirements

• Visual Studio 2008 for software development with yFiles WPF.
• Microsoft .NET Framework 3.0 or 3.5 to execute yFiles WPF programs.
• Microsoft Internet Explorer 6.0 or higher, Mozilla Firefox 2.0 or higher to browse the documentation.
• A Microsoft Windows operating system that supports the Windows Presentation Foundation.

yFiles WPF 2.0.1 - Changes Since 2.0.0.2

Improvements

• Made SimpleLabelStyle aware of RightToLeft flow direction of the GraphControl. The renderer now automatically mirrors the text contents to compensate the transform that has already been applied to the GraphControl.
• Improved the CollapsibleNodeStyleDecorator's renderer code to workaround an issue in WPF that prevents the FlowDirection dependency property from properly being considered in the decorator.
• The IReparentNodeHandler interface has been improved to now contain a callback that handles the actual reparenting of a node. This makes it possible to add additional callbacks and custom implementations for interactively reparented nodes.
• MultiplexingInputMode has been improved to automatically replace Cursor instances reported by concurrent child instances so that for FlowDirection settings of RightToLeft in the CanvasControl the cursors are mirrored horizontally. For this callback method ReplaceCursor has been added.
• NavigationInputMode and CanvasControl have been improved to be aware of the FlowDirection property of the CanvasControl so that in case of a RightToLeft setting the commands behave correctly.
• New overloads have been added in GraphMLIOHandler to the AddRegistryInputHandler and AddInputMapperFuture methods that make common tasks more easy to implement.

Bugfixes

• Fixed an exception in the undo code that occurred in the context of FoldingManager when nodes where moved into a collapsed group node.
• Fixed a problem that resulted in edges created interactively where there were no port candidates available but the CreateEdgeInputMode.ConncectToPortCandidatesOnly property was set to false had the wrong source port location model assigned. This resulted in these edges unexpectedly jumping to the mouse cursor.
• Fixed an exception that occurred when disabling shared references in GraphMLIOHandler.
• The setter of the property LocalCrossingMinimization in yWorks.yFiles.Layout.Router.OrthogonalEdgeRouter behaved incorrectly. This has been fixed. Also the property CustomBorderCapacityEnabled had no setter. The property has been renamed to UseCustomBorderCapacity and the getter has been reenabled.

Incompatible Changes

• The two previously undocumented methods in the layout's yWorks.yFiles.Algorithms.Node class Successors and Predecessors have now been documented and implemented correctly (the implementation of the two methods has been swapped).
• The IReparentNodeHandler interface has been changed to contain the new ReparentNode method. Existing implementations can simply delegate to the default implementation in ReparentNodeHandler.
• Code that replaced the navigational commands to honor the FlowDirection property of the CanvasControl needs to be replaced because the implementations will now automatically mirror the behavior in case of a RightToLeft setting.
• The first parameter of yWorks.yFiles.Layout.Hierarchic.Incremental.ILayers.Insert has been corrected to be of type yWorks.yFiles.Layout.Hierarchic.Incremental.LayerType
• GraphMLIOHandler's method AddRegistryInputHandler previously resulted in a runtime exception if there was a mapper in the registry with the same tag. The new implementation will either reuse the existing instance if it matches the type signature or remove the old instance prior to registering a new one. Method CreateMapper may be overwritten to adjust this default behavior.
• The property LocalCrossingMinimization in yWorks.yFiles.Layout.Router.OrthogonalEdgeRouter did not work as expected. The behavior has now been adjusted and thus changed. Also the read-only property CustomBorderCapacityEnabled has been renamed to a read-write property UseCustomBorderCapacity.

yFiles WPF 2.0.0.2 - Changes Since 2.0.0.1

Bugfixes

• Fixed a NullReferenceException in the context of IFoldedGraph that could happen in multi-level node collapse operations as a result to calls to Collapse.

yFiles WPF 2.0.0.1 - Changes Since 2.0

Bugfixes

• Fixed an exception (about unit being disposed already) in UndoEngine if an IUndoUnit was added within the AutoAddTimeSpan to the machine after the engine had been cleared.
• Calling IHierarchy.SetParent where the new parent was previously declared a leaf (instead of a group node) caused problems because the fact that the node now no longer was leaf was not published through an event. This resulted in inconsistent display of the views if the FoldingManager was used. Also the leaf state was not correctly rolled back during undo.
• All built-in GraphML DOMInputHandler could not parse GraphML default attribute values.
• Fixed incorrect implementation of various BridgeManager.RegisterXXXObstacle methods.
• The GroupingKeys.MinimumNodeSizeDpKey was not automatically added to the LayoutGraphAdapter. Now a DataProvider is added to the adapter graph that yields the minimum sizes for nodes that can be obtained from the ISizeConstraintProvider<INode> in the node's lookup.
• Fixed code in FixedGroupLayoutStage that threw a NullReferenceException and rendered the stage basically useless.
• Fixed exception in FixedGroupLayoutStage when orthogonal routing was specified, but no DataProvider for selected nodes was set.
• Fixed "Inconsistent Grouping" exception in IncrementalHierarchicLayouter.