Color; import java. Component; import java. EventQueue; import java. GridBagConstraints; import java. GridBagLayout; import java. Insets; import javax. JFrame; import javax. JPanel; import javax. UIManager; import javax. BOTH; gbc. Improve this answer. MadProgrammer MadProgrammer k 21 21 gold badges silver badges bronze badges. Great thank you, it's almost what I'm looking for : The only issue I'm having and that I cannot fix after my tests is the fact that the Panel below the orange one, at the right of the 4x2 one, takes the height of the 4x2 panel.
If possible, I'd like the 4x2 panel to take the height of this 1x1 panel, that should have the height of the other panels on the right of the window. I managed to get the right one to the good size, but the 4x2 panel stays the same and doesn't fit. This is no guarantee as other facts like the minimum size of the components might play a role in the determination of the overall height supplied to the row. Also, things like the fill property may also have an influence — MadProgrammer.
In my case I'm adding buttons inside the panels, and the difference is even bigger. Is their a way to avoid that? Not really. The problem, as I can see it, comes down to a mixture of factors. The preferred and minimum size of the panels and the insets. Because of specialized API like this, you do not need to know which layout manager if any many Swing containers use.
For the curious: scroll panes happen to use a layout manager named ScrollPaneLayout. For information about how to add components to a specific container, see the how-to page for the container. You can find the component how-to pages using How to Use Various Components. Sometimes you need to customize the size hints that a component provides to its container's layout manager, so that the component will be laid out well.
You can do this by specifying one or more of the minimum, preferred, and maximum sizes of the component. Here is an example of making a component's maximum size unlimited:. Many layout managers do not pay attention to a component's requested maximum size. However, BoxLayout and SpringLayout do. Furthermore, GroupLayout provides the ability to set the minimum, preferred or maximum size explicitly, without touching the component.
Besides providing size hints, you can also provide alignment hints. For example, you can specify that the top edges of two components should be aligned. You set alignment hints either by invoking the component's setAlignmentX and setAlignmentY methods, or by overriding the component's getAlignmentX and getAlignmentY methods.
Although most layout managers ignore alignment hints, BoxLayout honors them. You can find examples of setting the alignment in How to Use BoxLayout.
This website is written in English, with text that runs from left to right, and then top to bottom. However, many other languages have different orientations. The componentOrientation property provides a way of indicating that a particular component should use something different from the default left-to-right, top-to-bottom orientation. In a component such as a radio button, the orientation might be used as a hint that the look and feel should switch the locations of the icon and text in the button.
In a container, the orientation is used as a hint to the layout manager. To set a container's orientation, you can use either the Component -defined method setComponentOrientation or, to set the orientation on the container's children as well, applyComponentOrientation.
The argument to either method can be a constant such as ComponentOrientation. The example shows a button, a tree component, and a text area component in the window. If we create an empty tree component, there are some default values inside the component. The implicit layout manager of the JPanel component is FlowLayout. We do not have to set it manually. The flow layout manager sets a preferred size for its components.
So in our case, the area component will be xpx. If we didn't set the preferred size, the component would have a size of its text. Without the text, the component would not be visible at all. Try to write or delete some text in the area component. The component will grow and shrink accordingly. The GridLayout layout manager lays out components in a rectangular grid.
The container is divided into equally sized rectangles. One component is placed in each rectangle. The example shows a skeleton of a simple calculator tool. We put nineteen buttons and one label into the manager. Notice that each button is of the same size. Here we set the grid layout manager for the panel component. The layout manager takes four parameters. The number of rows, the number of columns and the horizontal and vertical gaps between components. BorderLayout is a simple layout manager that can be handy in certain layouts.
It has a serious limitiation — it sets the gaps between its children in pixels, thus creating rigid layouts. This leads to non-portable UI, and therefore, its usage is not recommended. BorderLayout divides the space into five regions: north, west, south, east, and centre. Each region can have only one component. If we need to put more components into a region, we have to put a panel there with a manager of our choice. The components in N, W, S, E regions get their preferred size. The component in the centre takes up the whole space left.
It does not look good if child components are too close to each other. We must put some space among them. Each component in Swing toolkit can have borders around its edges. To create a border, we either create a new instance of an EmptyBorder class or we use a BorderFactory.
Here we placed the top panel into the bottom panel component. More precisely, we placed it into the center area of its BorderLayout manager.
Here we created a 20px border around the bottom panel. The border values are as follows: top, left, bottom and right. Note that creating fixed insets spaces is not portable. The example shows a typical application skeleton. We show a vertical and horizontal toolbars, a statusbar, and a central component a text area.
BorderLayout is the default layout manager for the JFrame container. So we do not have to set it explicitly. In order to put some empty space around the button, we have to use EmptyBorder. This adds some fixed space to the top and bottom of the button. When we add fixed spaces, the UI is not portable.
A 3 px space may look OK on a x screen but it is inappropriate on a x px screen. CardLayout is a simple layout manager that treats each component as a card.
The container is a stack of these cards. Only one component is visible at a time; the rest is hidden. The first component added to the container is visible by default when the container is initially displayed. This manager has a limited practical use.
0コメント