-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
5.0
-
generic
-
generic
Name: dmR10075 Date: 03/30/2004
Users often want to indicate that some process is in progress by setting
WAIT_CURSOR on GUI components. Also, to disable further interaction with
GUI, they disable it. Unfortunately, disabled components show default
cursor, JavaDoc for Component.setCursor declares that - so these two
actions can't work at the same time. However, on native level there is
no such limitation. Since it comes from the implementation complexity,
not from the practical necessity, we should better provide such
possibility to users.
However, changing specification at this time might be impossible(the
change was made in 1999), so the alternative solution might be to
provide additional API or additional behavior, not contradicting with
current.
The proposed changes:
1) Modify the behavior so that when heavyweight is disabled, the cursor
over it and all over his children is the same as one set on heavyweight
or inhereted from parent(similar to Win32 API). The notion of
heavyweight can be restricted to toplevels.
2) Add possibility to set cursor globally. When it is set, it overrides
all cursor settings inside "global domain" until it is reset to
null(similar to Delphi and Win32 API). "Global domain" may be all
toplevels, whole device, or one toplevel.
3) Modify the behavior by removing the limitation for disabled
components.
======================================================================
Users often want to indicate that some process is in progress by setting
WAIT_CURSOR on GUI components. Also, to disable further interaction with
GUI, they disable it. Unfortunately, disabled components show default
cursor, JavaDoc for Component.setCursor declares that - so these two
actions can't work at the same time. However, on native level there is
no such limitation. Since it comes from the implementation complexity,
not from the practical necessity, we should better provide such
possibility to users.
However, changing specification at this time might be impossible(the
change was made in 1999), so the alternative solution might be to
provide additional API or additional behavior, not contradicting with
current.
The proposed changes:
1) Modify the behavior so that when heavyweight is disabled, the cursor
over it and all over his children is the same as one set on heavyweight
or inhereted from parent(similar to Win32 API). The notion of
heavyweight can be restricted to toplevels.
2) Add possibility to set cursor globally. When it is set, it overrides
all cursor settings inside "global domain" until it is reset to
null(similar to Delphi and Win32 API). "Global domain" may be all
toplevels, whole device, or one toplevel.
3) Modify the behavior by removing the limitation for disabled
components.
======================================================================
- relates to
-
JDK-4145822 setCursor fails when invoked before or after setEnabled
-
- Closed
-