| Summary: | [Markers] Problems tab title should only be shown in bold if there are any problems | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Max Gilead <max.gilead> |
| Component: | IDE | Assignee: | Tod Creasey <Tod_Creasey> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | minor | ||
| Priority: | P5 | CC: | daniel_megert, eclipse, joerg.heinicke, markus.kell.r, ondrej.chylik, tlane, Tod_Creasey |
| Version: | 3.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Max Gilead
Actually it shows bold whenever the count of items in the problems view changes. Many people also want to see thier warnings so not notifying of new warnings would be a regression. If you filter out your warnings you can get this behaviour. I would like to nudge this bug, as I find the current behaviour annoying and counter-productive. I frequently keep the console open in the same stack of tabs as the problems view; thus the problems view is often not visible to me. The current behaviour means that it's often impossible to know whether there are any problems without actually activating the problems view. Thus I find myself constantly switching between the console and the problems view, just to determine if there are any problems. This problem is exacerbated by the fact that the bold formatting is used to indicate change, not content. Further, Eclipse used to show the top error in a red font in the status line, which meant that you could at least see whether there was an error; but it no longer does this. The best solution I can think of is to make the problems tab title reflect the number of problems, but perhaps only if the view is not shown. Eg., "Problems [6]" would mean that the list contains 6 unfiltered errors. Another possibility is to render the inactive tab title in a red font. *** Bug 61035 has been marked as a duplicate of this bug. *** Are there any plans to fix this bug? Currently it's THE most annoying thing in Eclipse IMHO. Actually I learned to completely ignore Problems tab since I don't introduce errors that often and it's a waste of time to click on it and click back to another view each time I save a file. This leads to horrible thing - sometimes (when I do introduce an error) I discover it during a test run, NOT immediately after introducing it -- IMHO the Problems view bolding algorithm (and possibly other tabs as well as discussed in bug #69621) is so horribly broken I can't express it enough. Dear Eclipse developers! This feature is SO broken that is makes #1 fantastic feature of Eclipse - its compiler error/warning reporting useless since user doesn't even see these messages. IMHO the KISS rule should be applied here -- if there are ANY unfiltered errors/warnings (possibly configurable) after last compile, make Problems tab bold. If there are NO errors/warnings -- make it regular. If some users really do need indication of changed errors/warnings count -- use italic to indicate that. I can think of a several situations when current behavior is not a problem: - you've got 2-monitor setup and screen space is not a problem (did that, indeed solves issue) - you work on a code that's so problematic you introduce errors all the time (in this case you've got Problems tab opened all the time) Probably the worst situation is mine -- I introduce bugs rarely (hence don't need Problems tab opened all the time) and work on widescreen laptop (limited screen space). If current behavior is really usable to anyone (I can't imagine why would anyone care if bug count went up or down from X to Y without seeing actual bug list, but I guess people have different needs :) ) please at least introduce a configuration switch (eg. "Show Problems tab title in bold only if there are any errors"). Or do what Alex suggested -- ANYTHING will be better than current behavior. Problems view doesn't show bold any more. (In reply to comment #6) > Problems view doesn't show bold any more. FYI I've logged bug #282585 on 3.4 dropping support for bolding the Problems view. If that functionality comes back, this bug may once again be valid. |