AnchorPane allows the edges of child nodes to be anchored to an offset from the anchor pane's edges.
The Background of a
The fill and associated properties that direct how to fill the background of a
Defines properties describing how to render an image as the background to some
Defines the size of the area that a BackgroundImage should fill relative to the Region it is styling.
The Border of a
Defines properties describing how to render an image as the border of some Region.
BorderPane lays out children in top, left, right, bottom, and center positions.
Defines the stroke to use on a Border for styling a Region.
Defines the style of the stroke to use on one side of a BorderStroke.
Defines widths for four components (top, right, bottom, and left).
Defines optional layout constraints for a column in a
The base class for defining node-specific layout constraints.
Defines the radii of each of the four corners of a BorderStroke.
FlowPane lays out its children in a flow that wraps at the flowpane's boundary.
GridPane lays out its children within a flexible grid of rows and columns.
HBox lays out its children in a single horizontal row.
Base class for layout panes which need to expose the children list as public so that users of the subclass can freely add/remove children.
Region is the base class for all JavaFX Node-based UI Controls, and all layout containers.
Defines optional layout constraints for a row in a
StackPane lays out its children in a back-to-front stack.
TilePane lays out its children in a grid of uniformly sized "tiles".
VBox lays out its children in a single vertical column.
Enumeration of options for repeating images in backgrounds
Enum indicating the repetition rules for border images.
Enumeration used to determine the grow (or shrink) priority of a given node's layout area when its region has more (or less) space available and multiple nodes are competing for that space.
Provides classes to support user interface layout. Each layout pane class supports a different layout strategy for its children and applications may nest these layout panes to achieve the needed layout structure in the user interface. Once a node is added to one of the layout panes, the pane will automatically manage the layout for the node, so the application should not position or resize the node directly; see "Node Resizability" for more details.
The scene graph layout mechanism is driven automatically by the system once
the application creates and displays a
The scene graph detects dynamic node changes which affect layout (such as a
change in size or content) and calls
requestLayout(), which marks that
branch as needing layout so that on the next pulse, a top-down layout pass is
executed on that branch by invoking
layout() on that branch's root.
During that layout pass, the
layoutChildren() callback method will
be called on each parent to layout its children. This mechanism is designed
to maximize layout efficiency by ensuring multiple layout requests are coalesced
and processed in a single pass rather than executing re-layout on on each minute
change. Therefore, applications should not invoke layout directly on nodes.
The scene graph supports both resizable and non-resizable node classes. The
isResizable() method on
Node returns whether a
given node is resizable or not. A resizable node class is one which supports a range
of acceptable sizes (minimum <= preferred <= maximum), allowing its parent to resize
it within that range during layout, given the parent's own layout policy and the
layout needs of sibling nodes. Node supports the following methods for layout code
to determine a node's resizable range:
public Orientation getContentBias()
public double minWidth(double height)
public double minHeight(double width)
public double prefWidth(double height)
public double prefHeight(double width)
public double maxWidth(double height)
public double maxHeight(double width)
Non-resizable node classes, on the other hand, do not have a consistent
resizing API and so are not resized by their parents during layout.
Applications must establish the size of non-resizable nodes by setting
appropriate properties on each instance. These classes return their current layout bounds for
min, pref, and max, and the
resize() method becomes a no-op.
For example, a Button control (resizable) computes its min, pref, and max sizes which its parent will use to resize it during layout, so the application only needs to configure its content and properties:
However, a Circle (non-resizable) cannot be resized by its parent, so the application needs to set appropriate geometric properties which determine its size:
Button button = new Button("Apply");
Circle circle = new Circle(); circle.setRadius(50);
For example, to override the preferred size of a ListView:
Or, to change the max width of a button so it will resize wider to fill a space:
For the inverse case, where the application needs to clamp the node's min or max size to its preferred:
And finally, if the application needs to restore the intrinsically computed values:
layoutBoundsproperty to define the 'logical' bounds of the node for layout and
boundsInParentto define the visual bounds once all effects, clipping, and transforms have been applied.
These two bounds properties will often differ for a given node and
layoutBounds is computed differently depending on the node class:
|Node Type||Layout Bounds|
||Includes geometric bounds (geometry plus stroke). Does NOT include effect, clip, or any transforms.|
||logical bounds based on the font height and content width, including white space.
can be configured to be tight bounds around chars glyphs by setting
||Union of all visible childrens' visual bounds (
So for example, if a
DropShadow is added to a shape,
that shadow will not be factored into layout by default. Or, if a
ScaleTransition is used to
pulse the size of a button, that pulse animation will not disturb layout around
that button. If an application wishes to have the effect, clip, or transform
factored into the layout of a node, it should wrap that node in a Group.
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 2008, 2017, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.