Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 69621

Summary: [Markers] Problems view needs a better bolding algorithm
Product: [Eclipse Project] Platform Reporter: Dani Megert <daniel_megert>
Component: IDEAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 CC: jan.diederich
Version: 3.0Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard: stalebug
Bug Depends on: 282585    
Bug Blocks:    

Description Dani Megert CLA 2004-07-08 11:12:02 EDT
R3.0

1. start fresh workspace
2. create Java project "JUnit"
   (accept to switch to Java perspective)
3. import JUnit source into "JUnit"
4. Ctrl+H
5. switch to "Java Search" page
6. check "Search the JRE system libraries"
7. click "All occurrences"
8. click Method
9. enter toString
10. click Search
11. click "Run in Background"
12. observe: Search view title is italic
13. give focus to Problems view and wait
14. observe: Search view title (might) turn bold
15. give focus to Search view
16. context menu > Search Again
17. click "Run in Background"
18. give focus to Problems view and wait
19. observe: Search view title *does not* turn bold (sometimes a quick bold
title might be visible).

I could reproduce this with other scenarios e.g. first search then add some
error to the code and save ==> Problems view did not get bold title.
Comment 1 Tod Creasey CLA 2004-07-14 11:53:23 EDT
I can't replicate this using your steps in 3.0. The problems view will not 
bold if the list of errors is the same size as the one when the recalculation 
started.
Comment 2 Dani Megert CLA 2004-07-19 06:22:44 EDT
Please, try several times. It is definitely broken. I had this while demoing the
feature during a talk and then later when repeating the steps for this PR.

>The problems view will not 
>bold if the list of errors is the same size as the one when the recalculation 
>started.
So mean if I have ErrorA and ErrorB and after building ErrorC and ErrorD it will
not change to bold since the size is the same? Well, that's a bug then anyway.
Comment 3 Tod Creasey CLA 2004-07-19 08:26:10 EDT
For sure it is a limitation that that is what we are doing - we were concerned 
about performance and so didn't explore a better algorithm in 3.0..

I'll reopen and rename it appropriate
Comment 4 Tod Creasey CLA 2004-07-19 08:27:12 EDT
Stefan the issue Dani is seeing is that we do not show bold if the number of 
problems has not changed. As a result it is possible to fix a problem and 
introduce a new one but not get a visual indication.
Comment 5 Tom Hofmann CLA 2006-01-25 06:26:44 EST
related to / dup of bug 75602.

Note that I even see the bold title when there are no entries before and after a build.

I usually filter anything but errors, which results in an empty view most of the time - I find myself clicking the problems view almost automatically to clear the bold title nowadays... It would be cool if 'bold' really meant 'something has changed'.
Comment 6 Jan-Hendrik Diederich CLA 2008-02-28 09:38:23 EST
(In reply to comment #5)
> 
> I usually filter anything but errors, which results in an empty view most of
> the time - I find myself clicking the problems view almost automatically to
> clear the bold title nowadays... It would be cool if 'bold' really meant
> 'something has changed'.
Well, that leads to another question: in this case there are changes. Should the bould-ness be related to all changes or only to changes which aren't filterd?
I think this should be configurable.
 

Comment 7 Dani Megert CLA 2009-07-16 02:31:13 EDT
Bolding is broken in since 3.4, see bug 282585.
Comment 8 Eclipse Webmaster CLA 2019-09-06 16:06:36 EDT
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.
Comment 9 Eclipse Genie CLA 2021-11-26 14:47:48 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.