Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359144 - Problems window should receive focus if a build has problems
Summary: Problems window should receive focus if a build has problems
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 17:04 EDT by eclipse CLA
Modified: 2011-11-18 11:02 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description eclipse CLA 2011-09-27 17:04:56 EDT
Build Identifier: 20100917-0705

When I run a build, I get no indication whether the build succeeded unless I manually switch to the Problems window

Expected result:
The problems window gains focus
a) when any build detects new problems
b) when I manually trigger a build, whether or not any problems were detected

There should exist a preference checkbox to enable or disable this behavior, possibly a radio button or dropdown to choose between a), b), or neither.  See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=6783

Reproducible: Always

Steps to Reproduce:
1. Type random garbage in a file
2. Project | Build All
Comment 1 Remy Suen CLA 2011-11-18 10:14:33 EST
Dani I think I've seen an old bug about this topic. Do you remember such a discussion?
Comment 2 Dani Megert CLA 2011-11-18 10:56:49 EST
(In reply to comment #1)
> Dani I think I've seen an old bug about this topic. Do you remember such a
> discussion?

Since 3.7/4.1 the Problems view indicates any issue in its icon, even if the view is hidden in a stack or docked as fast view. I think this can be closed.
Comment 3 Remy Suen CLA 2011-11-18 11:02:04 EST
(In reply to comment #2)
> Since 3.7/4.1 the Problems view indicates any issue in its icon, even if the
> view is hidden in a stack or docked as fast view. I think this can be closed.

Yes, I suppose the decorator implemented by bug 170244 should satisfy most use cases.