Originally posted by Craig Wood:
It is generally not a good idea to be calling
'setVisible' on components in a top–level container to control their visibility. You
can add/remove components (followed by a call to validate/revalidate to the parent) or
use a CardLayout or, in some cases, a JTabbedPane.
edit: adjust width
[ October 07, 2005: Message edited by: Craig Wood ]
First of all, thanks for the quick reply.
I thought that putting all of the controls to my forms while showing a splash screen would be a good idea, because the JRE would have time to arrange everything as it wishes, and setting each panel's visibility would take no time at all, as the components are already on their places. Why is calling setVisible() on their containers a wrong idea? I am not sure that JTabbedPane is good for me, and I do not know CardLayout at all, I'll play with them.
What does "edit: adjust width" mean?
Regards,
Brian