-
Enhancement
-
Resolution: Fixed
-
P4
-
6
-
b24
-
generic
-
generic
Name: dmR10075 Date: 03/04/2004
Window.setAlwaysOnTop API has been implemented so that user is unable to
tell whether his Window has actually became always-on-top or not. This
is because many platforms don't guaranteely support (even when declared)
the support for always-on-top windows. However, it is very bad practice
to have such an API without the means to get the accomplicity feedback.
I propose to add a new method, Toolkit.isAlwaysOnTopSupported, which
returns either three-state value("supported","not supported","unknown")
or two-state value("supported", "not supported" and "unknown" are
merged).
======================================================================
Window.setAlwaysOnTop API has been implemented so that user is unable to
tell whether his Window has actually became always-on-top or not. This
is because many platforms don't guaranteely support (even when declared)
the support for always-on-top windows. However, it is very bad practice
to have such an API without the means to get the accomplicity feedback.
I propose to add a new method, Toolkit.isAlwaysOnTopSupported, which
returns either three-state value("supported","not supported","unknown")
or two-state value("supported", "not supported" and "unknown" are
merged).
======================================================================