I think what you are trying to say here, is that there are some cases
when we show
a platform native dialog. I presume we can't shape those .. so it isn't
the same case
as creating our own window. If you really want to drop those words, then
OK, but in
my opinion it is better with them in. So what is the final text you
propose ?
This below ?
> Visual effects such as halos, shadows, motion effects and animations may
> be applied to the window by the desktop window management system.
> These are outside the knowledge and control of the AWT and so for the
> purposes of this specification are not considered part of the
top-level window.
-phil.
On 4/14/20, 12:55 AM, Sergey Bylokhov wrote:
On 4/13/20 8:38 am, Philip Race wrote:
we just do not specify what is
"AWT-defined window" means and why for example the
JDialog/JFileChooser/etc are
AWT-defined.
Well, I think we need it. It means what the Java application
requested. Simple enough.
I missed your point here, we need what? I provided an example of
JFileChooser(I found another one - JOptionPane)
top-level windows which are per-spec unrelated to the AWT.
