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 43547 - [50cat] debugger view does not maintain last selected view.
Summary: [50cat] debugger view does not maintain last selected view.
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
: 45364 47935 55563 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-05-19 13:25 UTC by zikmund
Modified: 2008-12-22 14:47 UTC (History)
7 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zikmund 2004-05-19 13:25:13 UTC
When running a project in debugger, 3 debug
windows open (Watches, Local Variables, Call
Stack). Everytime you invoke debugger, Watches
window is on top. I'd prefer to use last used
debug window (from previous debugging session) to
have on the top.
My motivation: Watches are not the most used debug
window, IMHO it's Local Variables (you can add
watches only after you have some local variable
context), but using last used debug window should
be good for all users.

If not possible to have last used window
information, please change it to Local Variables
-- as I mentioned, it seems to be the most used
debug window after running debug session.
Comment 1 _ rkubacki 2004-08-02 14:21:12 UTC
debugger folks please evaluate. Probably depends on debugger user view. 
Comment 2 Jan Jancura 2004-08-02 15:23:12 UTC
This functionality is not specified in Debugger Users View. But last
selected view should be on the top - seems natural to me.
Comment 3 Milos Kleint 2004-08-04 12:10:07 UTC
reassigning
Comment 4 Milos Kleint 2004-08-06 06:56:39 UTC
you use the topcomponentgroup apis which don't say anything about last
selected on top. It's not even possible, given that the TCs can span
multiple modes and each mode can also contain TC that are not part of
the group. if you want to provide such functionality (and deal with
all the corner cases or ignore them), remember the selected one and
when reopening call requestvisible on that one.
Comment 5 Milos Kleint 2004-08-06 08:27:07 UTC
*** Issue 45364 has been marked as a duplicate of this issue. ***
Comment 6 Jan Jancura 2004-08-26 16:42:19 UTC
*** Issue 47935 has been marked as a duplicate of this issue. ***
Comment 7 Jan Jancura 2004-08-26 16:46:14 UTC
Once more. This piece of code is not in debugger. Its feature of
window system. If it should be fixed, it should be fixed there.
I will not provide any hacks for your bugs. Take care about this
issue, please.
I see 3 user complains about this problem, so its probably not corner
case for our users.
Comment 8 Milos Kleint 2004-08-26 16:59:14 UTC
I've read the APIs, UI spec..

Please point me to the documentation where it's said that we guarantee
the ordering of opened TCs in a TCGroup. 
And maintain this in time.
All the TCGroups provides is coordinated opening and closing of TCs. 
It's not bug on winsys side. We implement everything that's in the spec.

Please don't reassign back without additional reasoning.

Comment 9 Jan Jancura 2004-08-26 17:25:17 UTC
This is not debuggercore issue.
Comment 10 Milos Kleint 2004-08-27 08:32:55 UTC
it's definitely not a bug of the winsys either. We follow the spec as
it now. If the spec gets updated, we will provide the functionality,
either with or without adding APIs. For the time being however it's up
to you if you want to maintain the last selected on top or not. I've
given you hints how to do it only.
Comment 11 Milos Kleint 2004-08-27 08:47:35 UTC
Jano, can you please update the UI spec for winsys to deal with the issue?

what to do with selected/visible TCs in the IDE when opening and
closing the TC group?
Comment 12 lleland 2005-03-19 19:45:38 UTC
Updated to 41cat.
Comment 13 David Simonek 2005-04-22 14:42:51 UTC
to jjancura: mkleint is right, but I think your opinion is understandable. Just
without these strong words next time, pretty please... 

To the problem: It seems natural that winsys is good place for supporting
requested feature, unfortunately I see impl as problematic, as group can be in
many states, during opening and closing and it's not always clear what the
desired action should be. I mean that some of group's windows may be already
closed during group close or already opened during group open. How should system
behave then? Could such functionality be disabled or always enabled?
Comment 14 David Simonek 2005-04-22 14:44:23 UTC
*** Issue 55563 has been marked as a duplicate of this issue. ***
Comment 15 johnzoet 2005-04-24 00:12:07 UTC
I checked this on Mandrake Linux 10.1 
Whatever debugger window is on top stays on top. 
 
Comment 16 clever 2005-10-27 14:34:32 UTC
I'd like to extend this to maintain the window prefs between NB installs.  Every
time I use a new build, I always have to reposition my debugger windows to a
more sensible place. I attached my layout, for the heck of it. Maybe the default
location can be changed to this too.
Comment 17 David Simonek 2005-10-27 15:03:11 UTC
clever, sorry but no, no extensions of this issue, file separate enhancement
request please if you want so. And just keep in mind that settings import
between day to day builds isn't supported and will never be IMHO, this is simply
unmanageable. 
Comment 18 Jesse Glick 2008-05-22 16:08:40 UTC
Please reevaluate.
Comment 19 Stanislav Aubrecht 2008-07-22 17:09:26 UTC
i tried nb080721 and the debugger windows do remember their positions and the last active window - closing