Bug 76830 - [Progress] Can't use IProgressService.showInDialog with IWorkbenchWindowConfigurer.setShowProgressIndicator(false)
Summary: [Progress] Can't use IProgressService.showInDialog with IWorkbenchWindowConfi...
Status: RESOLVED DUPLICATE of bug 90508
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 76833 76834 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-22 13:24 EDT by Stephen Goldbaum CLA
Modified: 2006-02-02 11:37 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Goldbaum CLA 2004-10-22 13:24:18 EDT
In an RCP app with the ProgressIndicator in the StatusBar is turned off.  If 
you use the progress dialog to show a job's progress (via 
PlatformUI.getWorkbench().getProgressService().showInDialog(shell, job)) and 
the job has an exception or the user presses "Run in Background", it causes 
the following:


java.lang.NullPointerException
	at org.eclipse.ui.internal.progress.ProgressManagerUtil.animateUp
(ProgressManagerUtil.java:328)
	at 
org.eclipse.ui.internal.progress.ErrorNotificationDialog.initializeBounds
(ErrorNotificationDialog.java:375)
	at org.eclipse.jface.window.Window.create(Window.java:351)
	at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:925)
	at org.eclipse.jface.window.Window.open(Window.java:637)
	at 
org.eclipse.ui.internal.progress.ErrorNotificationManager$3.runInUIThread
(ErrorNotificationManager.java:154)
	at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:93)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:106)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2749)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2434)

A simple check in ProgressMonitorUtil.animateUp() to check whether the 
ProgressRegion is null should fix this.
Comment 1 Kim Horne CLA 2004-10-22 14:20:57 EDT
*** Bug 76833 has been marked as a duplicate of this bug. ***
Comment 2 Kim Horne CLA 2004-10-22 14:21:16 EDT
*** Bug 76834 has been marked as a duplicate of this bug. ***
Comment 3 Tod Creasey CLA 2006-02-02 11:37:18 EST

*** This bug has been marked as a duplicate of 90508 ***