Radial Layout
This section describes the major changes to the RadialLayout class.
As with other major layout algorithms, the RadialLayout class no longer inherits from MultiStageLayout, but instead implements ILayoutAlgorithm directly. The layout stages are now managed by a LayoutStageStack, which can be obtained via the layoutStages property; see Layout Stages and Multi-Stage Layouts for more details.
Renamed, Moved, and Removed Classes and Members
The following table contains the renamed, moved, and removed classes and members of the major classes of the RadialLayout.
yFiles for HTML 2.6 | yFiles for HTML 3.0 | Remarks |
---|---|---|
Changed Default Values and Behavior Changes
Node labels are now considered by default. To change this behavior, set the nodeLabelPlacement property to the desired value. This property allows switching between all integrated node labeling policies and placing the node labels with GenericLabeling.
Edge labels are now placed by the GenericLabeling algorithm by default. To change this behavior, set the edgeLabelPlacement property to the desired value.
Port placement now takes the specified port candidates into account. Port candidates can be specified via the properties on the sub-data RadialLayoutData.ports. The ports are placed in a post-processing step by the PortPlacementStage.
If custom layers are defined via the RadialLayoutData.layerIds property, these are
considered automatically, and the value of RadialLayout.layeringStrategy is ignored.
It is no longer necessary to set it to RadialLayoutLayeringStrategy.USER_DEFINED
, which consequently has been removed.
If custom center nodes are defined via the RadialLayoutData.centerNodes property, these
are considered automatically, and the value of RadialLayout.centerNodesPolicy is ignored.
It is no longer necessary to set it to CenterNodesPolicy.CUSTOM
, which consequently has been removed.