Bug 99954 - [Dialogs] [Progress] Need a dialog with an embedded progress monitor
Summary: [Dialogs] [Progress] Need a dialog with an embedded progress monitor
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 99947
  Show dependency tree
 
Reported: 2005-06-14 09:35 EDT by Dirk Baeumer CLA
Modified: 2019-09-06 16:08 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Baeumer CLA 2005-06-14 09:35:57 EDT 
RC2

We have new build path actions which ask for some minor user input. The action
itself is exexuted as a runnable. To improve the UI a dialog with an embeeded
progress monitor would be helpful. A refactoring dialog is a little bit to heavy
weight.
Comment 1 Dirk Baeumer CLA 2005-06-14 09:37:32 EDT 
Search has such a dialog as well (ExtendedDialogWindow)
Comment 2 Tod Creasey CLA 2005-06-14 10:11:00 EDT 
Why not use a ProgressMonitorPart in your dialog?
Comment 3 Dirk Baeumer CLA 2005-06-14 10:27:19 EDT 
Then you have to do the whole enablement/disablement logic by yourselve. The
dialog as the wizards should be an IRunnableContext.
Comment 4 Susan McCourt CLA 2007-07-02 19:40:57 EDT 
changing prio and status to conform to plat-ui bug guidelines
Comment 5 Susan McCourt CLA 2009-07-09 15:57:01 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:08:45 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.