Shared-State Race Condition

Using null layouts (and relying on manual bounds positioning) leaves Swing without layout management, so component placement is not consistently computed and components default to the top when bounds/updates are not handled correctly. | Newly added UI elements always appear at the top of the window and ignore attempts to change their positions, preventing the intended inline button layout. | Remove null layouts and avoid manual positioning with setBounds; instead, use an appropriate Swing LayoutManager (e.g., FlowLayout/BoxLayout/BorderLayout/GridLayout) to place components correctly.