Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340100

Summary: [Progress] org.eclipse.ui.internal.operations.TimeTriggeredProgressMonitorDialog might open twice
Product: [Eclipse Project] Platform Reporter: Janice Li <jli1>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: prakash, remy.suen
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Proposed Change
none
Proposed changes none

Description Janice Li CLA 2011-03-15 18:13:45 EDT 
Build Identifier: 

In org.eclipse.ui.internal.operations.TimeTriggeredProgressMonitorDialog, 'dialogOpened' is only set to true in 'checkTicking()'. If 'dialog.open()' is called directly, 'dialogOpened' remains false, and 'checkTicking()' might call 'open()' again.

In our use case, we have a credential dialog on the top of TimeTriggeredProgressMonitorDialog. Before we open the credential dialog, we will check if the TimeTriggeredProgressMonitorDialog is open. If not, call 'dialog.open()' to open it. The symptom of 'open()' being called twice is: after credential dialog is open on the top of progress dialog, progress dialog 'open()' is called again and grab the focus in the back. User's activity on the credential dialog might be interrupted.

Reproducible: Always
Comment 1 Janice Li CLA 2011-03-15 18:20:06 EDT 
Created attachment 191259 [details]
Proposed Change

Proposed changes, but not in patch format.
Comment 2 Janice Li CLA 2011-03-15 18:32:17 EDT 
Created attachment 191260 [details]
Proposed changes

Not sure how to delete the first attachment. But this one is better.
Comment 3 Lars Vogel CLA 2019-11-08 04:39:54 EST 
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.

If the bug is still relevant please remove the stalebug whiteboard tag.