Bug 82107 - [Progress] WorkbenchSiteProgressService should not refer to WorkbenchPart directly
Summary: [Progress] WorkbenchSiteProgressService should not refer to WorkbenchPart dir...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-01-03 16:17 EST by Nick Edgar CLA
Modified: 2021-09-16 20:07 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2005-01-03 16:17:08 EST
build I20041221

WorkbenchSiteProgressService.runInUIThread has:
    // TODO: should not access WorkbenchPart directly -- IWorkbenchPart defines
the API
    if (part instanceof WorkbenchPart)
        ((WorkbenchPart) part).showBusy(busy);


See bug 82106 for a recommendation.
Comment 1 Tod Creasey CLA 2005-04-27 14:57:50 EDT
The comment is wrong. I have removed it
Comment 2 Nick Edgar CLA 2005-04-27 15:17:26 EDT
No, the issue is the same as in bug 82106.  The workbench should only talk to
parts via IWorkbenchPart and sub-interfaces.  WorkbenchPart is on the
client-side of the API and is just a convenience implementation of IWorkbenchPart.

If a mix-in for showBusy is not going to be added, the comment should be left in.
Comment 3 Tod Creasey CLA 2007-06-14 12:53:30 EDT
There are currently no plans to work on this although we would be happy to review a patch
Comment 4 Susan McCourt CLA 2009-07-09 19:36:37 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:31:00 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 6 Eclipse Webmaster CLA 2019-09-06 15:37: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 7 Eclipse Genie CLA 2021-09-16 20:07:17 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. 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.