Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325253 - Java Stack Trace Console should be a separate panel and not a part of the Console panel
Summary: Java Stack Trace Console should be a separate panel and not a part of the Con...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-14 09:58 EDT by Thorbjørn Ravn Andersen CLA
Modified: 2010-09-14 10:11 EDT (History)
4 users (show)

See Also:

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 Thorbjørn Ravn Andersen CLA 2010-09-14 09:58:15 EDT 
Build Identifier: 20100617-1415

The Java Stack Trace Console panel is very useful and I tend to need it all the time.  Also the Console panel is very useful to see what my program actually prints, but the two for some reason are in the same view, making it difficult at best to use them both.  As they are logically different (even if they share some implementation) it would make sense to have the Java Stack Trace console a separate panel.  It might even track the contents of the clipboard, making it even easier to navigate to an error location.  Ctrl-C, see it in the panel, click the line.

Reproducible: Always

Steps to Reproduce:
1.Open Java Stack Trace Console 
2.Run program
3.Console switches away from Stack Trace Console.
Comment 1 Remy Suen CLA 2010-09-14 10:00:31 EDT 
Couldn't you just spawn new console views?
Comment 2 Olivier Thomann CLA 2010-09-14 10:04:19 EDT 
Move to JDT/UI
Comment 3 Dani Megert CLA 2010-09-14 10:07:59 EDT 
You can have two separate consoles and pin them. Suggest to close as WONTFIX.
Comment 4 Darin Wright CLA 2010-09-14 10:11:47 EDT 
Marking as works for me. Use the "New Console View" action in the console drop down toolbar action to open a new console. You can open a stack trace console there and then pin the view (toolbar action) so it does not track the active process output.