Bug 94166 - [Progress] - need progress dialog that opens after given elapsed time
Summary: [Progress] - need progress dialog that opens after given elapsed time
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks: 94164
  Show dependency tree
 
Reported: 2005-05-09 13:27 EDT by Susan McCourt CLA
Modified: 2009-08-30 02:11 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 Susan McCourt CLA 2005-05-09 13:27:42 EDT 
For 3.1, I implemented TimeTriggeredProgressDialog in 
org.eclipse.ui.internal.operations.  It opens only after the specified time 
has elapsed.  This would be a good general-purpose dialog.

Even better would be if this dialog could be reused to run multiple 
runnables.  Currently users of ProgressMonitorDialog have to create a new 
dialog every time they run something.  It would be nicer if they could create 
the dialog once and run runnables with it.  This feature would also allow the 
OperationHistoryActionHandlers to share the progress reporting with the 
undo/redo operation approvers that run during the running of the handler.  
(See bug #94164)
Comment 1 Susan McCourt CLA 2005-05-24 14:17:43 EDT 
I mentioned in the previous comment that reusing the dialog would allow the 
action handlers to share the dialog with the operation approvers that run 
during the running of the action handler.  

A problem caused by having to use multiple dialogs is that the dialog attempts 
to show a busy cursor prior to running the runnable.  Once the busy cursor is 
on, another dialog is created for the operation approver, which also turns on 
(and then off) the busy cursor.  This means the busy cursor doesn't show in 
some scenarios.  (See bug #94410).  If this dialog could be used multiple 
times with different runnables, we could probably address this issue.
Comment 2 Susan McCourt CLA 2005-05-24 15:27:11 EDT 
I originally opened this bug to suggest that JFace provide a progress dialog 
that opens after a given elapsed time.

Since then, I've run into some issues with nested use of the progress monitor 
(see bug #94164).  Reusing the dialog won't really help, and my problem isn't 
as general purpose as I've thought.

It seems a more specific progress dialog for my case would be needed.  (One 
whose monitor could handle multiple begin task/tick/done sequences, creating a 
new sub progress monitor each time, so that clients could treat the monitor as 
if it were brand new.)

At any rate, this bug remains open to request the generic feature, and to also 
request that there be protected protocol for creating the progress monitor, so 
that subclasses could provide custom solutions without the mess of wrappering 
them.
Comment 3 Tod Creasey CLA 2006-04-07 13:00:14 EDT 
There are currently no plans to work on this feature as we have busyCursorWhile in the workbench
Comment 4 Denis Roy CLA 2009-08-30 02:11:02 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.