Community
Participate
Working Groups
When there are errors, the problems view does not pop-up or get activated, and there is no way of configuring it to do so. This is counter-intuitive, and not in line with other views, e.g. the debug view, the search view, which pop-up or activate when they are invoked. This would be particularly useful for the problems view, as generally you want to be alerted if there are build errors. Also useful for those who like to have an editor-centric view, i.e. maximise the editor for the most amount of screen real estate, and have other views pop-up when activated. Suspect this would also help those migrating from other IDEs where this is a default behaviour. Suggest this is at least made configurable for those who want it.
We used to do this. See the discussion in bug 45336 that led to removal of this feature.
Thanks for the context. What I could see us doing is decorating the problem view's icon when there are errors (similar to the changing icon for the JUnit view when the tests are running or have failed).
Also see related discussion in bug 274116. The old ProblemView class implements bolding the view title after a build completes in which the problem count changed. This was a more subtle form of the "activate problem view" behaviour. That bolding behaviour wasn't implemented in the new ProblemsView class (not sure if that change was intentional or not). The general form of the problem here and in bug 274116 is "what affordance should we show when a build completes".
Remy is now responsible for watching the [ViewMgmt] category.
(In reply to comment #2) > What I could see us doing is decorating the problem > view's icon when there are errors (similar to the changing icon for the JUnit > view when the tests are running or have failed). The icon is now being updated with a decorator with the fix for bug 170244. http://download.eclipse.org/eclipse/downloads/drops/S-3.7M3-201010281441/images/problems-view-icon.png Is this a satisfactory solution for you, Peu?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
