Well, it ran fine, when I tried it under 1.4.2_10, but some comments:
you don't need javax.swing.SwingUtilities.invokeAndWait in init.
There's no painting until well after init has finished, so doing GUI
stuff in init is safe. You only need that in some special cases, as I
explain here (if your browser supports the use of applets) :
http://javalessons.com/cgi-bin/ui/java-swing.cgi?1cd=ths&sid=ao789
Another thing, why not add the components to FileChooserPanel straight
away, instead of putting them in other panels first ?
Hope this helps,
---
Paul Hamaker, SEMM
http://javalessons.com
Thomas Hawtin - 24 Dec 2005 15:35 GMT
> Well, it ran fine, when I tried it under 1.4.2_10, but some comments:
> you don't need javax.swing.SwingUtilities.invokeAndWait in init.
> There's no painting until well after init has finished, so doing GUI
> stuff in init is safe. You only need that in some special cases, as I
Sun's information on this is contradictory. In fact, you do need the
invokeAndWait to be safe, as Swing (particularly text) is booby-trapped
with invokeLaters.
> explain here (if your browser supports the use of applets) :
> http://javalessons.com/cgi-bin/ui/java-swing.cgi?1cd=ths&sid=ao789
Or use appletviewer from the JDK.
Tom Hawtin

Signature
Unemployed English Java programmer
http://jroller.com/page/tackline/