This is present in all java versions.

There are many glaring holes in AWT which have been present since JDK 1.0, yet which Sun has refused to fix.  Presumably this is because they are not present in Swing, and Sun wants developers to use Swing instead of AWT .  Unfortunately, this is not always an option.  Swing applications are MUCH slower and use MUCH more memory than AWT applications.  In addition, trying to mix lightweight and heavyweight components in a single window causes serious problems.  There are many technologies which require the use of heavyweight components: Java3D is a prime example, as well as 3rd party libraries such as Quicktime for Java and GL4Java.  For these reasons, using Swing often is not an option.

Among the most serious holes are the following:

- Dialogs should be able to have menu bars.
- FileDialogs should have a "select folder" mode.
- FileDialogs should use FilenameFilters, and not simply ignore them.
- TextAreas should offer both line wrap and word wrap.
- TextComponents should allow using multiple fonts and styles within a single component.
- AWT should offer true floating windows.
- It should be possible to set a default button for a window or dialog.

The lack of these features seriously limits the usefulness of Java for writing true applications, especially for developers who need to use native rendering libraries such as Java3D, or who cannot accept the speed and memory overhead which Swing requires.
(Review ID: 117623) 
======================================================================

N/A

I'm not sure how this ended up in Swing, reassigning to AWT.
 xxxxx@xxxxx  2001-02-27

A little more explanation.  Most of the functionality requested is 
mentioned under separate rfes.  FileDialog Filter is a good example of this.  

As far as performance, 1.3 is much, much faster than 1.2.  1.4 will be even 
faster than 1.3.  
 xxxxx@xxxxx  2001-03-20