Community
Participate
Working Groups
Issue: The progress dialog box is not visible during eclipse startup if cancel is enabled: getSite().getWorkbenchWindow().getWorkbench().getProgressService() .run(true,true, runnable); However: The progress dialog box is visible during eclipse startup if cancel is disable: getSite().getWorkbenchWindow().getWorkbench().getProgressService() .run(true,true, runnable); The same behaviour in Eclipse Version 3.1.2.
Sorry for typo - The progress dialog box is visible during eclipse startup if cancel is disabled: getSite().getWorkbenchWindow().getWorkbench().getProgressService() .run(true,false, runnable);
Can you give me more details please. Are you trying to execute something in a dialog during startup? If so are you doing it on the startup of your plug-in. Note that will have trouble starting something before the workbench is started. If you could give me a quicky example plug-in that would help a lot.
I have developed an eclipse plugin that is able to parse a very larg file(e.g. 500 MB) during the startup of the workbench. There is a different behaviour of the progress dialog box: 1. If cancel is disabled(run(true,false, runnable)): The progress dialog box is visible during the startup of the workbench. 2. If cancel is enabled(run(true,true, runnable)): The progress dialog box is not visible during the startup of the workbench. Why ? Due to this behaviour the user is not able to cancel the parsing process of the lange file. Code snippet: IRunnableWithProgress runnable = new IRunnableWithProgress() { public void run(IProgressMonitor monitor) throws InvocationTargetException, InterruptedException { try { parseFileAndPropagateDataToMonitor(); monitor.done(); } catch (...) { } } }; try { getSite().getWorkbenchWindow().getWorkbench().getProgressService().run(true, true, runnable); } catch (...){ }
The new launcher support in 3.3 allows you to show progress in the launch dialog - that is now out recommended way to handle this sort of issue.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.
