This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 11837 - Frame's maximized state is not handled correctly
Summary: Frame's maximized state is not handled correctly
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: _ ttran
URL:
Keywords:
: 18167 25335 25476 (view as bug list)
Depends on:
Blocks: 26984
  Show dependency tree
 
Reported: 2001-04-30 07:36 UTC by onivy
Modified: 2008-12-23 09:35 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description onivy 2001-04-30 07:36:29 UTC 
to reconstruct:
	1. maximize a window.
	2. close the window.
	3. reopen the window.
	result: the window is not maximized, but in the size of the screen 
                i.e. the window's middle icon is maximize.
	the user can't restore the original size and position of the window.
Comment 1 Jan Zajicek 2001-05-02 14:41:11 UTC 
Please provide more information such as build # etc. I tested this on nb3.2
build #38 and everything works well.
Comment 2 Jan Chalupa 2001-05-05 20:35:09 UTC 
Target milestone -> 3.3
Comment 3 onivy 2001-05-06 08:50:51 UTC 
the bug was reconstructed on 3.2 release build.
Comment 4 Jiri Rechtacek 2001-10-18 10:31:05 UTC 
It is a issue in window system.

The behavior has changed a little:
[SDI]
1. open window on size1
2. resize it on size2
1. maximize a window
2. close it
3. reopen it.
Result: normalized window, size is size1

[MDI]
1. open window on size1
2. resize it on size2
1. maximize a window
2. close it
3. reopen it.
Result: maximized window, after normalize then window has size1
Comment 5 Jan Chalupa 2001-11-27 11:53:25 UTC 
Target milestone -> 3.3.1.
Comment 6 Jan Chalupa 2001-11-27 11:56:59 UTC 
Target milestone -> 3.3.1.
Comment 7 _ ttran 2001-11-29 16:06:23 UTC 
changed the "Summary" to more accurately reflect the problem.

The trouble is that on JDK 1.3 java.awt.Frame does not know about
Maximized/Minimized state.  This has been fixed in JDK 1.4.  We will
have to either drop support for JDK 1.3 or find a way to run the
needed code when JDK 1.4 is detected (reflection?)
Comment 8 _ ttran 2001-11-29 16:14:13 UTC 
*** Issue 18167 has been marked as a duplicate of this issue. ***
Comment 9 David Simonek 2001-11-29 16:21:08 UTC 
yes, reflection when 1.4 is detected is the best way (for user) to go,
although not very nice from programmer's point of view.
As for issue 18167 - it is talking specifically about main window -
keep in mind that there is also missing support for persisting
normal/maximized state of main window into xml file
(WindowManager.wswmgr), so this will have to be included in the fix as
well.
Comment 10 Jiri Rechtacek 2001-12-03 17:24:31 UTC 
Assigning back to Dafe.
Comment 11 Jan Chalupa 2002-01-11 14:04:11 UTC 
Target milestone -> 3.4
Comment 12 Jan Chalupa 2002-01-11 14:08:12 UTC 
Target milestone -> 3.4
Comment 13 Jan Chalupa 2002-01-11 14:09:08 UTC 
Target milestone -> 3.4
Comment 14 Jan Chalupa 2002-01-11 14:11:48 UTC 
Target milestone -> 3.4
Comment 15 David Simonek 2002-05-28 15:37:37 UTC 
passing to winsys guys.
Comment 16 Marian Mirilovic 2002-06-20 15:15:57 UTC 
Marek, you have fixed something like this, or no ?
Comment 17 Peter Zavadsky 2002-06-21 16:42:29 UTC 
It is working now, closing as worksforme.
Comment 18 _ ttran 2002-07-04 15:00:29 UTC 
no it still doesn't work.  We need to use reflection to call JDK 1.4
Frame.{set,get}ExtendedState()
Comment 19 _ ttran 2002-07-04 15:01:48 UTC 
*** Issue 25335 has been marked as a duplicate of this issue. ***
Comment 20 _ ttran 2002-07-04 15:12:29 UTC 
actually this issue has nothing to do with minimized state, updated
"Summary"
Comment 21 _ ttran 2002-07-04 15:15:42 UTC 
Fixed.  One need to run the IDE with JDK 1.4
Comment 22 _ ttran 2002-07-10 10:02:47 UTC 
*** Issue 25476 has been marked as a duplicate of this issue. ***
Comment 23 mslama 2002-09-04 13:37:51 UTC 
Trung you changed XML for window manager -> new DTD -> update
apichanges. Please next time either do necessary update of let us know
so that we can do that.
Comment 24 Marian Mirilovic 2002-10-30 13:34:34 UTC 
verified in [nb_dev](20021030)
Comment 25 Quality Engineering 2003-07-01 16:37:26 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 26 Jan Chalupa 2003-11-03 11:33:07 UTC 
*** Issue 25476 has been marked as a duplicate of this issue. ***
Comment 27 Jan Chalupa 2003-11-03 11:59:53 UTC 
*** Issue 25335 has been marked as a duplicate of this issue. ***