RFE for BugID: 4092033
---------------------------------
RFE from the customer:
We fear the current fix for the above case (pre fix behaviour: window did not
get active once moved toFront(), post fix behaviour: window gets active once
moved toFront()) even though it satifies the request raised by Deutsche Boerse
Systems may trigger complaints from other Java developers as they might rely on
the current behaviour and expect the window not to be come activated once moved
toFront(). We suggest to expand the set of allowed parameters of the
Frame.setState(int) method by two additional states ACTIVE and NOACTIVE. This
would allow software developers to independently change z-ordering of windows
using toFront(), toBack() and the window activity state using setState( ACTIVE)
or setState(NOACTIVE) as required.
---------------------------------
RFE from the customer:
We fear the current fix for the above case (pre fix behaviour: window did not
get active once moved toFront(), post fix behaviour: window gets active once
moved toFront()) even though it satifies the request raised by Deutsche Boerse
Systems may trigger complaints from other Java developers as they might rely on
the current behaviour and expect the window not to be come activated once moved
toFront(). We suggest to expand the set of allowed parameters of the
Frame.setState(int) method by two additional states ACTIVE and NOACTIVE. This
would allow software developers to independently change z-ordering of windows
using toFront(), toBack() and the window activity state using setState( ACTIVE)
or setState(NOACTIVE) as required.
- relates to
-
JDK-4092033 window.toFront() method is now also setting focus
-
- Resolved
-
-
JDK-4487944 LINUX:setState(Frame.NORMAL) is not triggering WindowActivated Event.
-
- Closed
-