Bug 197967 - [Progress] Refactor TimeTriggeredProgressMonitorDialog to a publicly accessable package
Summary: [Progress] Refactor TimeTriggeredProgressMonitorDialog to a publicly accessab...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-26 10:04 EDT by Stefan Baramov CLA
Modified: 2019-09-06 15:30 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Baramov CLA 2007-07-26 10:04:25 EDT
Currently the TimeTriggeredProgressMonitorDialog is placed in  org.eclipse.ui.internal.operations package making it internal component. However great number of application can benefit if this was a public component. For example: consider a "parent-child" UI construct. The master element is a tree widget. A selection in the tree widget determines the content of the child widget, e.g. table widget. However, to loading the content of the child widget is a long running operation. A progress dialog need to be displayed each time a selection is made in the master widget. This could result in a "flashing" dialog.  A dialog showing just for a fraction of second. The TimeTriggeredProgressMonitorDialog solves this problem in a very elegant way. 

I would like to suggest moving the TimeTriggeredProgressMonitorDialog to a public packages such as org.eclipse.jface.dialogs or org.eclipse.ui.dialogs. 

Thanks
Stefan
Comment 1 Kim Horne CLA 2007-08-07 11:10:08 EDT
Incidentally, this bit me in the bum while I was trying to do some custom RCP work awhile back.  Having this available would be quite useful.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:30:34 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.