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 90467 - Debugger does not remember last panel
Summary: Debugger does not remember last panel
Status: VERIFIED DUPLICATE of bug 90134
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: Other Windows ME/2000
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-01 23:22 UTC by tkellerer
Modified: 2006-12-04 07:28 UTC (History)
0 users

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 tkellerer 2006-12-01 23:22:59 UTC
Every time I start a new debug session NetBeans chooses one of the panels
seemlingy randomly. It is *never* the panel that I chose to display during the
last run. The only rule that I can detect when displaying the panel is: "Never
display the one that the user wants to see". 

Re-ordering the panels does not make any difference, e.g. I start a debug
session. The panels are order: Call Stack, Watches, Local Variables, with "Call
Stack" beeing the active one.
So I select "Local Variables" because I'm not interested in the others. Then I
end the debugger session. do some coding, debug again. Now the "Call Stack" is
*again* the active one (even though I ended the last debugger session with
having the local variables active).

As in both cases the leftmost tab is activated, I re-order the tabs to make the
local variables the left one. Then I start a debug session. But now the Call
stack is *again* the active stack (but now beeing the middle one)

This is *very* annoying. Is there any logic that choses the active tab? If so
I'd like to understand it, to make sure the local variables are always the
active tab when I start a debug session (I know I can simply close the others,
but that seems a very ugly workaround)
Comment 1 Martin Entlicher 2006-12-02 00:16:05 UTC
We do know about this, but it's not explored yet. Our opinion is that the window
system is involved. It's actually already submitted as issue #90134.
We understand that this is a usability problem, it will be definitely solved
into NB 6.0.

*** This issue has been marked as a duplicate of 90134 ***
Comment 2 Jiri Kovalsky 2006-12-04 07:28:22 UTC
Verified as duplicate of already known P2 issue.