Community
Participate
Working Groups
I am now seeing bold and italic fonts in my views. I have no idea what these mean. Where does the idea of using italics to mean "in progress" come from? What about overlaying an [animated] hourglass decorator icon on the view's icon. Of course, you'd have to be showing icons for views all the time (or at least when busy). Related, every time I change selection in the workbench, the problems view temporarily changes to italics. It is a flicker which lasts for about 1/10th of a second, and is pretty annoying.
> Of course, you'd have to be showing icons for views all the time Actually, I take that back. If a view is hidden, then what is the point of telling the user that what they can *not* see is not up-to-date? This type of information should only be displayed if a view is visible.
This was selected as the most noticable way to display it. Icons generally require too much change to make them noticable enough. We may look into animated icons in 3.1.
Even so, the views such as Tasks and Problems are briefly flickering italics. Also, what about only using Italics for views which are visible. It is nothing but distracting for background views to change their tab font.
We have decided that consistency was key - all busy tabs are showing italics as it wasn't clear to the user why italics would show up some times and not others. Bold is only shown when there has been a change and only if it is not in focus for the reasons you outline.
So the flicker is W.A.D.?
Randy do you mean that it is happening too fast - i.e. you think there should be a timing delay?
Yes, it is too fast. It shows up for like 1/10th of a second. Set the Tasks view to be "On Selected Resource and Children". Every single selection change causes the italics to appear (as long as the new selection has a different set of tasks). In addition, the entire view stack flickers, perhaps CTabFolder is calling redraw(...) on an area which is larger than just the tabitem which is being updated. For some reaons, problems view does not show italics as often even though it has the same filter settings. And it actually has more items in it which would take longer to populate and filter.
I have renamed this PR to deal with the flicker issue
Thanks Randy - I have replicated this. I am going to mark down its priority however as we need to focus on some bigger problems now.
There are currently no plans to work on this although we would be happy to review a patch
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
This is not Progress view item rather Markers view. Changing the Summary and QA contact accordingly. Hitesh, Guess this should not happen after your changes. Check and update the bug accordingly.
(In reply to comment #12) > This is not Progress view item rather Markers view. Changing the Summary and QA > contact accordingly. > > Hitesh, > Guess this should not happen after your changes. Check and update the bug > accordingly. I tried this with 3.6, it is not as frequent on my system. The view's implementation has undergone significant changes since 3.0. The flicker should no longer be an issue; as for the italicization of title, this is the least distracting UI affordance IMO. This would be a more general issue , if at all. I intend to close this bug unless there is some related pending issue specific to the markers view.
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.
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.
