Bug 168081

Summary:	[Progress] Show actual progress in view icon
Product:	[Eclipse Project] Platform	Reporter:	Markus Keller <markus.kell.r>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	bpasero, kelvinc, kpeter, mik.kersten
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Markus Keller

2006-12-14 11:45:19 EST

I20061214-0010

The view progress animation would be much more useful if it would show the actual progress. E.g. in the Search or Call Hierarchy views, the user can see the actual progress (xx% done) in the Progress view (and sometimes in the window trim).

An overlay on the view icon could be used to show the xx% done right where it belongs. We already have something like this in the JUnit view (only when the view is minimized) and I think it works pretty well there.

Comment 1 Tod Creasey

2006-12-15 08:22:51 EST

That progress animation only shows busy and not busy state. We don't have the concept of progress currently in the views so this would require new API.

In the case of views like Problems and the Package Explorer it shows that it is busy while computations it has no feedback from are running (marker generation and decoration respectively) so I think it would only be useful in some views that use this feature now.

Perhaps a gradient on the tab would look nice as well.

Comment 2 Markus Keller

2007-01-16 09:14:22 EST

> Perhaps a gradient on the tab would look nice as well.

Maybe, but that would not be visible when views are minimized in the 3.3 presentation (where minimized views are reduce to icons in separate fast view bars).

Comment 3 Tod Creasey

2007-06-19 16:27:27 EDT

We are not currently looking into this issue.

Comment 4 Susan McCourt

2009-07-09 19:37:51 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 5 Eclipse Webmaster

2019-09-06 16:16:04 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.