Specifies whether or not the separately laid out components of the input graph should be arranged by this class.

By default this feature is enabled.

Specifies the current component spacing. This value represents the minimum allowed distance between the bounding boxes of to components.

Determines whether or not to take node and edge labels into account when calculating the bounding box of the graph components.

By default this feature is enabled.

See also

Specifies the current grid spacing. Components will be moved by multiples of this value, thus keeping their offset to the grid. That way, components or parts of them that were placed on a grid before, will stay on their original grid. The grid spacing also influences the distance between the components.

Note that this option keeps existing grid locations intact but won't correct the location of a component to the grid specified here.

If grid spacing equals 0, the grid won't be considered at all.

Getter: Determines whether or not grouping information bound to the graph will be used to calculate the components.

The default value is true.

The default value is true.

Specifies the preferred layout size for this layouter.

See also

Specifies the component arrangement style used by this ComponentLayouter.

The default is STYLE_ROWS.

See also

Initializes a new ComponentLayouter instance.

See also

Produces a non-overlapping component graph layout. This method moves the graph components in such a fashion that their bounding boxes do not overlap. The arrangement strategy used takes the ratio of the overall layout area into account.

Parameters

Parameters

Calculates and returns the bounding box of a graph component including node halos. This method will be invoked for each component of the graph. Depending on the state of property labelAwarenessEnabled the returned bounding box will also take node and edge labels into account.

Parameters

Determines if the preconditions for the graph layout algorithm are fulfilled, by applying them to the connected components.

Parameters

Calculate the layout. This is done by decomposing the graph in its connected components and applying the core layout algorithm on each component.

Parameters

See also

Determines which nodes will belong to the same graph component. Additionally to normal connectedness a group node and all of its children will belong to the same component.

Parameters

Initializes this object. See the documentation of the corresponding factory method newComponentLayouter1() for details.

See also

Initializes this object. See the documentation of the corresponding factory method newComponentLayouter2() for details.

Parameters

See also

Initializes a new ComponentLayouter instance.

See also

Initializes a new ComponentLayouter instance.

Parameters

See also

Sets the origin for a subgraph.

Parameters

Sets the preferred layout size for this layouter.

Parameters

See also

DataProvider key that can be used to determine components by hand. The algorithm will use the com.yworks.yfiles.base.DataProvider.getObject() method to query for object instances that will be used to determine components: If null is returned for a node that node's component will be determined as usual. If non-null values are returned, they will be compared using their natural order ( com.yworks.bridge.util.Comparable) to determine the component order.

See also

DataProvider key that can be used to determine which nodes should be laid out. Note that components will be laid out if and only if at least one of the nodes that make up the component returns true if queried through the DataProvider instance. If no such instance is registered with the graph, all components will be laid out by the core layout algorithm.

Use this constant for masking actual styles constants from style modifiers.

See also

Modifier constant that can be added to normal style constants to indicate that the arrangement strategy should take the initial positions of the components into account. Combining this modifier is supported with the following styles: STYLE_SINGLE_ROW, STYLE_SINGLE_COLUMN, STYLE_PACKED_RECTANGLE, STYLE_PACKED_COMPACT_RECTANGLE, STYLE_PACKED_CIRCLE, and STYLE_PACKED_COMPACT_CIRCLE.

See also

Modifier constant that can be added to normal style constants to indicate that the arrangement strategy should produce a non-overlapping component layout. Combining this modifier is supported with STYLE_NONE.

Note that non-overlapping component layout (in the sense that no elements from adjacent components overlap) is inherently supported by the following styles: STYLE_PACKED_RECTANGLE, STYLE_PACKED_COMPACT_RECTANGLE, STYLE_PACKED_CIRCLE, and STYLE_PACKED_COMPACT_CIRCLE.

See also

Style specification constant describing a component arrangement strategy that places components in multiple rows. In contrast to STYLE_ROWS, each row may also be divided into further sub-rows, thus especially being advantageous, if there are few very large components and many significantly smaller ones. The strategy tries to arrange the components such that the aspect ratio of the final component placement gets as close as possible to the aspect ratio of the preferred layout size, configurable using setPreferredLayoutSize().

See also

Style specification constant describing a component arrangement strategy that places components in multiple rows. In contrast to STYLE_ROWS, each row may also be divided into further sub-rows, thus especially being advantageous, if there are few very large components and many significantly smaller ones. The strategy tries to arrange the components such that the aspect ratio of the final component placement gets close to the aspect ratio of the preferred layout size, configurable using setPreferredLayoutSize() . But in contrast to STYLE_MULTI_ROWS, this strategy tries not always to come as close to the preferred view ratio, if not necessary, i.e. if a ratio close to the preferred ratio only induces a lot of unused view space. This unused space will be minimized.

See also

Style specification constant describing a component arrangement strategy. It uses the same core strategy as STYLE_MULTI_ROWS, but under the restriction that the resulting height does not exceed the preferred height ( preferredLayoutSize). Note, that the preferred width and thus the aspect ratio will be ignored. In contrast to STYLE_MULTI_ROWS_HEIGHT_CONSTRAINED_COMPACT, the result will be an arrangement which uses as much height as possible, even if that means that all components will be arranged in one single column.

See also

Style specification constant describing a component arrangement strategy. It uses the same core strategy as STYLE_MULTI_ROWS, but under the restriction that the resulting height does not exceed the preferred height ( preferredLayoutSize). Note, that the preferred width and thus the aspect ratio will be ignored. In comparison with STYLE_MULTI_ROWS_HEIGHT_CONSTRAINED, the result will be compacted, which means that an arrangement with the minimum width such that the height constraint is still fulfilled will be realized.

See also

Style specification constant describing a component arrangement strategy. It uses the same core strategy as STYLE_MULTI_ROWS, but under the restriction that the resulting width does not exceed the preferred width ( preferredLayoutSize). Note, that the preferred height and thus the aspect ratio will be ignored. In contrast to STYLE_MULTI_ROWS_WIDTH_CONSTRAINED_COMPACT the result will be an arrangement which uses as much space in width as possible, even if that means that all components will be arranged in a single row.

See also

Style specification constant describing a component arrangement strategy. It uses the same core strategy as STYLE_MULTI_ROWS, but under the restriction that the resulting width does not exceed the preferred width ( preferredLayoutSize). Note, that the preferred height and thus the aspect ratio will be ignored. In comparison with STYLE_MULTI_ROWS_HEIGHT_CONSTRAINED the result will be compacted, in order to minimize unused view space induced by components that are large in height.

See also

Style specification constant describing no special component arrangement at all. Components will be centered at the same position they resided at before the layout started. If combined with the style modifier STYLE_MODIFIER_NO_OVERLAP components might get moved so that they don't overlap after the layout.

See also

Style specification constant describing a component arrangement strategy that tries to place components like in a cloud around the biggest component. Entities of different components will not overlap, however the bounding boxes of the components may overlap.

See also

Style specification constant describing a component arrangement strategy that tries to place components like in a cloud around the biggest component. Entities of different components will not overlap, however the bounding boxes of the components may overlap. In contrast to STYLE_PACKED_CIRCLE components might even be placed in empty spaces inside other components.

See also

Style specification constant describing a component arrangement strategy that tries to place components like in a rectangular cloud around the biggest component. Entities of different components will not overlap, however the bounding boxes of the components may overlap. In contrast to STYLE_PACKED_RECTANGLE components might even be placed in empty spaces inside other components.

See also

Style specification constant describing a component arrangement strategy that tries to place components like in a rectangular cloud around the biggest component. Entities of different components will not overlap, however the bounding boxes of the components may overlap.

See also

Style specification constant describing a component arrangement strategy that tries to place components in multiple rows so that the overall aspect ratio of all components gets as close to the aspect ratio of the preferred layout size as possible.

See also

Style specification constant describing a component arrangement strategy that places components above each other in a single column. If combined with the style modifier STYLE_MODIFIER_AS_IS components will be placed in the same order as they were placed before the layout.

See also

Style specification constant describing a component arrangement strategy that places components next to each other in a single row. If combined with the style modifier STYLE_MODIFIER_AS_IS components will be placed in the same order as they were placed before the layout.

See also