Bug 222573 - Variables view panes should be two independent (but linked) views
Summary: Variables view panes should be two independent (but linked) views
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-13 10:02 EDT by Neale Upstone CLA
Modified: 2008-03-13 10:26 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Neale Upstone CLA 2008-03-13 10:02:25 EDT
Build ID: M20080221-1800

Steps To Reproduce:
Debug an application, and look at the variables view.
We get the choice of three layouts:
- Variables only
- Horizontal
- Vertical

What would be much better (and this applies to the JUnit view too), is to be able to move the two panes of the view independently, such that one can be tall and think, and one can be short and wide.

Both Variables and JUnit views would benefit from this option, as they are a compromise in terms of having a long vertical list to select, and then seeing the associated variable data (or stack trace) confined to a pane with a size constrained by the width of the other pane.

Practically, this could be implemented without a great upheaval.
1) Keep the 3 layout options
2) Add a view "Selected Variable"
3) Make the Selected Variable view listen to what is selected in the Variables view, and display that.

The same approach could be taken with JUnit.
Comment 1 Curtis Windatt CLA 2008-03-13 10:26:52 EDT
This would not be a trivial undertaking.  The variables, expressions and registers views all use the detail pane.  Eventually the memory view may use it as well.  there are already a lot of views available in the debug perspective, and it is preferred not to add more.  Also, there is a push for us to have multiple variables views each showing a different active debug context.  A separate details view would add complexity.

I won't close this request as I can see why it might be convenient for some users.  However, there are no plans to do this in 3.x