JDK-4490915 : Under Windows LAF UnMaximizable JInternalFrames are Maximized
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.3.1,1.4.0,1.4.1
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_nt,windows_2000
  • CPU: x86
  • Submitted: 2001-08-10
  • Updated: 2003-03-18
  • Resolved: 2003-03-18
Related Reports
Duplicate :  
JDK-4524996 - Auto-maximization of non-maximizable internal frames with Windows LAF
Duplicate :  
JDK-4424247 - DefaultDesktopManager does not handle InternalFrame state changes as expected.
Description

Name: bsC130419			Date: 08/10/2001


Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.0-beta_refresh-b72)
Java HotSpot(TM) Client VM (build 1.4.0-beta_refresh-b72, mixed mode)


The problem is that under Windows LAF frames that have their isMaximizable bit
explicitly set to false are still maximized due to the standard "MDI" behavior.

  1) Run SwingSet2 Demo (that would be the one in \demo\jfc\SwingSet2)
  2) Switch to Windows LAF
  3) Go to Internal Frames Demo
  4) Maximize one of the internal frames
  5) Click once on the "Internal Frame Generator" window handle (ie. title bar)

The Internal Frame Generator is now maximized and can't be unmaximized.  You
have to minimize and restore to put it back to default size.
(Review ID: 129495) 
======================================================================
Comments
EVALUATION I am able to reproduce the bug stated. It looks like this case, an internal frame always on top, is not currently supported correctly. I need to investigate this. ###@###.### 2001-09-20 This bug is being covered under bug 4424247 along with a number of other bugs that regarding internal frame state management. Please look at this new bug for more up to date information and references to other bugs. ###@###.### 2003-03-18
18-03-2003