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 90134 - [Study][DB-2] Debugger doesn't remember selected tab
Summary: [Study][DB-2] Debugger doesn't remember selected tab
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Stanislav Aubrecht
URL: http://ui.netbeans.org/usability/debu...
Keywords: USABILITY
: 90467 92798 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-28 08:50 UTC by jrojcek
Modified: 2008-12-22 10:05 UTC (History)
2 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 jrojcek 2006-11-28 08:50:33 UTC 
Finding	
Selected debugger tab wasn't persisted between debugging sessions. For example participant selected the 
Watches tab and restarted debugging session which automatically selected the Local Variables tab. Several 
participants commented this "buggy" behavior.

Severity	
This is a bug. Almost all participants were affected.

Recommendation	
Remember selected tab between debugging sessions (and also IDE sessions).
Comment 1 Martin Entlicher 2006-12-02 00:15:59 UTC 
*** Issue 90467 has been marked as a duplicate of this issue. ***
Comment 2 Martin Entlicher 2006-12-02 00:18:52 UTC 
This is a severe usability problem, which exists for a long time already.
It needs to be explored whether the problem is in window system or debugger.
Scheduling for 6.0.
Comment 3 Martin Entlicher 2006-12-19 13:18:43 UTC 
These are core issues. There are two bugs:
1) The order of the tabs is not preserved
2) The selected tab is not remembered

1) I've found the responsible code at
org.netbeans.core.windows.model.TopComponentSubModel.addOpenedTopComponent().
The code does not check the indexes of already opened components. Thus it
alteres the order.

2) TopComponentSubModel seems to be responsible as well. The
selectedTopComponentID is set to the first component that happens to be opened
(in addOpenedTopComponent() method). When the group is closed,
selectedTopComponentID is being set to other individual top componnets in
adjustSelectedTopComponent(), which effectively removes the information about
the last user-selected top component. previousSelectedTopComponentID contains
the stored value all the time, but does not seem to be used in the GUI.

Moving to core to fix this...
Comment 4 Martin Entlicher 2007-01-28 08:11:13 UTC 
*** Issue 92798 has been marked as a duplicate of this issue. ***
Comment 5 Stanislav Aubrecht 2007-02-13 09:52:32 UTC 
fixed in trunk

Checking in model/TopComponentSubModel.java;
/cvs/core/windows/src/org/netbeans/core/windows/model/TopComponentSubModel.java,v
 <--  TopComponentSubModel.java
new revision: 1.15; previous revision: 1.14
done
Checking in Central.java;
/cvs/core/windows/src/org/netbeans/core/windows/Central.java,v  <--  Central.java
new revision: 1.53; previous revision: 1.52
done