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 10601 - Some windows could remember their (default) position - so after "Undock View", they can reside on previous place.
Summary: Some windows could remember their (default) position - so after "Undock View"...
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P4 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords: ARCH
: 14959 (view as bug list)
Depends on:
Blocks: 18327
  Show dependency tree
 
Reported: 2001-03-22 16:58 UTC by Robert Dankanin
Modified: 2008-12-23 09:32 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
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 Robert Dankanin 2001-03-22 16:58:23 UTC 
[Main trunk build #151]

Try e.g. this:
1. start newly unzipped build (in SDI)
2. click on [Properties] title bar
3. choose "Window" -> "Dock View Into" -> "Explorer" -> "Bottom"
4. click on "Properties" tab in [Explorer] frame
5. choose "Window" -> "Undock"

-> [Properties] will appear right below MW on the left side of screen (zero 
position?), hidding part of [Explorer] that way
-> IMO it could be nice if some components could remember their initial (or 
previous) position - so e.g. in this case [Properties] could appear on the same 
place as it was by default before docking action was performed.
Comment 1 Jan Chalupa 2001-05-05 20:30:52 UTC 
Target milestone -> 3.3
Comment 2 Jan Chalupa 2001-11-27 11:49:55 UTC 
Target milestone -> 3.3.1.
Comment 3 Jan Chalupa 2001-11-27 11:53:20 UTC 
Target milestone -> 3.3.1.
Comment 4 Jan Chalupa 2002-01-11 14:02:44 UTC 
Target milestone -> 3.4
Comment 5 Jan Chalupa 2002-01-11 14:06:22 UTC 
Target milestone -> 3.4
Comment 6 Jan Chalupa 2002-01-11 14:07:44 UTC 
Target milestone -> 3.4
Comment 7 Jan Chalupa 2002-01-11 14:10:51 UTC 
Target milestone -> 3.4
Comment 8 David Simonek 2002-01-28 15:46:55 UTC 
Reassigning to Jiri for evaluation. Jiri, please check for duplications, think
about what these enhancements will need to be implemented right and write down
your observations and thoughts to the enhs themselves.
Comment 9 Jiri Rechtacek 2002-01-29 14:28:24 UTC 
Eval: The restore a undocked window to default size and location is
depends on solution issue 9308.
The restore a undocked window to previous state is intensive a little.
 We should store all information about mode in spite of the mode was
docked to else mode. These information could be used if mode is
undocked or docked in another mode.
Comment 10 mslama 2002-02-01 12:54:09 UTC 
Quot:
 We should store all information about mode in spite of the mode was
docked to else mode. These information could be used if mode is
undocked or docked in another mode.

IMHO it is nonsense: Mode cannot be docked to another mode. You dock
top component.

To this problem I suspect that when you undock new mode is created and
original mode is not reused. (Need to be confirmed.) In addition in
case of user mode we delete it when it is closed to avoid increasing
number
of modes in window system. It is not this case because original
Properties mode is not user mode so it could be reused but in other
case if it would be user mode it could not be resused because it does
nto exist anymore.
Comment 11 Marek Grummich 2002-07-22 08:36:48 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 12 Marek Grummich 2002-07-22 08:55:18 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 13 Peter Zavadsky 2002-07-24 09:20:31 UTC 
Seems a litlte design problem. It needs to be figured out what should
be stored: Last undocked mode for the TopComponent or the last
undocked(?)bounds of the TopComponent?
Comment 14 Peter Zavadsky 2002-07-24 10:22:20 UTC 
*** Issue 14959 has been marked as a duplicate of this issue. ***
Comment 15 Marian Mirilovic 2003-11-26 12:58:59 UTC 
Because Window System v1 will not be supported from now by our team, all old
winsys issues (now "core/window system v1" issues) are going to be closed as
WONTFIX. 

Changes in API which emerged both from UI spec 
and problems with adjusting to the older API are described in the document
http://core.netbeans.org/windowsystem/changes.html.
 It shows also recommends how the client code should be adjusted to the new
window system.

If you think this issue apply also to the new winsys then change the
subcomponent (to "core/window system") and REOPEN it.
Comment 16 Marian Mirilovic 2004-02-27 14:11:02 UTC 
issue doesn't apply to new window system - verified