yFiles WPF 2.2.0.2 Release Notes
yFiles WPF 2.2.0.2 is the newest bugfix and maintenance release available.
Technical Requirements
- Visual Studio 2008 or 2010 for software development with yFiles WPF
- Applications based on yFiles WPF require the Microsoft .NET Framework 3.5 SP1 runtime (or higher).
- A browser to view the HTML documentation.
- A Microsoft Windows operating system that supports the Windows Presentation Foundation.
yFiles WPF 2.2.0.2 - Changes Since 2.2.0.1
Bugfixes
ControlStyleBase.StyleTagwas not excluded from obfuscation.- Some table related classes were not excluded from obfuscation.
- Fixed exception in
LayoutExecutorwhen animation and grouping were both disabled. - Fixed potential memory leaks in
TableLayoutConfiguratorwhen exceptions occurred. yWorks.yFiles.Algorithms.Groups.EdgeBetweennessClustering: The parametersminGroupCountandmaxGroupCounthad no effect.
Automatic Layout
LayoutExecutordid not provide the GraphControl's selection to the layout engine.- Fixed
NullReferenceExceptioninPartitionGridLayoutStageif no partition cells were assigned to any nodes. - Fixed Exception that was triggered when using a generic labeling algorithm (i.e. a subclass of
yWorks.yFiles.Layout.Labeling.AbstractLabelingAlgorithm) together with layout stageyWorks.yFiles.Layout.LabelLayoutDataRefinement.
yFiles WPF 2.2.0.1 - Changes Since 2.2
Bugfixes
TableExtensions.RemoveWithResizealways resized the last sibling instead of the neighbor.- The
LabelDefaults.AutoAdjustPreferredSizewas ignored for stripe labels. TableEditorInputMode.TextEditorInputModewas used even when the TableEditorInputMode had been installed as child mode ofGraphEditorInputMode.TableEditorInputMode.DeleteSelection: Items were not always deleted in bottom to top order, leading to unpredictable resize results.TableLayoutConfiguratorused wrong bottom insets for the last column.TableLayoutConfiguratordid not correctly restore the mapper for partition cells that had been set explicitly.DefaultStripeInputVisualizationHelperwas not excluded from obfuscation.- Broken
AbstractTableNodeStyleimplementation resulted in defunct visuals if used in multiple CanvasControls and after export operations. NodeDropInputModedid not transfer focus to the graph control after a node had been dropped.- The
TagofIStripes in the default table implementation was not serialized and deserialized from and to GraphML. To get back that old behavior, set the newSerializationProperties.DisableStripeUserTagsproperty totrue. - The
GraphClipboarddid not always copy all state of items that were invisible in a folded graph view. - Dropping columns and rows into a table accidentally resized the parent stripe to values that are too small for the contents.
- For some configurations,
TableLayoutConfiguratorcould not properly deal with non-empty group nodes inside table nodes. - Fixed a bug that caused the
GraphCommands.CollapseGroupCommandandGraphCommands.ToggleGroupStateCommandto fail in case of certain multi-node selections.
Automatic Layout
EdgeGroupRouterStage: Edges that had both source and target group IDs were not grouped at all.









