Bonjour.
After spending countless hours around this site, looking for code to drag a component across the screen, I noticed that there is a strange trend in the answers.
... that everyone is trembling at the sound of a zero layout.
So, I ask, what does every problem have with this? I encoded no more than three months, using Swing no more than one, and the layout was a breeze using infinite customization is possible. Why is this a bad practice?
The main problem is the difficulty of trying to define specific platforms for things like fonts and pixel display methods.
, , - .
API , , DPI 120 DirectX, DPI 92 OpenGL.
( ) , .
Swing API API, , - , , , .
, , , . , , .
VB (, ), , , .
Swing - IMHO
. , , . .
. .
, , . , .
In other situations, the layout manager (or a combination of nested layout managers), if this is the best solution for developing effective graphical interfaces.
You will lose some points of the graphical interface for its use, because it is difficult to maintain, more code, less flexible ... Adding an additional button will lead to a large recalculation that you need to do.
As I see it: http://leepoint.net/notes-java/GUI/layouts/nulllayout.html