|
Quick Lists
|
|
Bug ID:
|
4227768
|
|
Votes
|
21
|
|
Synopsis
|
Z-ordering of Windows Look-and-Feel JInternalFrames
|
|
Category
|
java:classes_swing
|
|
Reported Against
|
1.2
, 1.1.6
, 1.2.1
, 1.2.2
|
|
Release Fixed
|
1.4(merlin-beta)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4166803
,
4238509
,
4245251
,
4253052
|
|
Submit Date
|
08-APR-1999
|
|
Description
|
Z-ordering of JInternalFrame "MDI" windows under Windows look-and-feel doesn't work properly. To see the problem, simply
1. run SwingSet under Windows look-and-feel.
2. create a few internal frame windows (say "Internal Frame 1" through "Internal Frame 4".
3. close the most recently created window ("Internal Frame 4").
4. Internal Frame 3 (the next frame in the stack) should then be on top, but instead Internal Frame 1 pops up! This is NOT the case with Java look-and-feel: only Windows look-and-feel.
It seems you are simply keeping internal frames in a list and if any internal frame is closed, the oldest frame created is shown.
This may seem like a trivial problem, but my users really hate this "feature". When you close a window, the next window in the stack should open.
(Review ID: 56491)
======================================================================
|
|
Work Around
|
I could try to maintain the correct stack myself.
======================================================================
|
|
Evaluation
|
Indeed, the internal frames seem to get activated in seemingly random order.
xxxxx@xxxxx 1999-09-16
We can remove remapping of the actions that switch to next
and previous frame in WindowsDesktopPaneUI and leave the original from
BasicDesktopPaneUI. Also the wrong activation in BasicDesktopPaneUI is
fixed (third file)
======================================================================
|
|
Comments
|
Submitted On 27-SEP-1999
ScottAdler
Even though this is an in-progress bug I cannot vote for it. What is up?
Submitted On 13-DEC-2000
delft
In JDK 1.3 this bug still seems to persist.
When will the fix be released?
Submitted On 16-JUL-2001
ninesun
Yes, this problem still exists in JDK1.3.
Submitted On 31-JAN-2002
orfant
This bug exists even in JDK 1.3.1_02, but is fixed in
1.4.0.rc
Submitted On 31-JAN-2002
orfant
This bug exists even in JDK 1.3.1_02, but is fixed in
1.4.0.rc
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |