Bug 202055 - [WorkbenchLauncher] Possibility to quit a splash handler with the standard org.eclipse.ui.PlatformUI exit codes.
Summary: [WorkbenchLauncher] Possibility to quit a splash handler with the standard or...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-03 04:41 EDT by Stefan Lötscher CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments
Interactive Splash Handler Template (6.82 KB, text/plain)
2007-09-03 04:43 EDT, Stefan Lötscher CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Lötscher CLA 2007-09-03 04:41:54 EDT
In order to show startup progress of a RCP application we use the new splash handler mechanism. We need to make several steps to start our application before the workbench is shown. A possible step in our startup procedure should be able to enforce a restart or a proper stop of the application. Unfortunately there is no such exit behaviour foreseen in the AbstractSplashHandler.

As an example look at the InteractiveSplashHandler template available from the product editor ("Interactive - A simulated log-in session"). Because of the missing exit functionality, "System.exit(0)" is called.

I think a better solution is to leave the splash handler with one of the following states PlatformUI.RETURN_RESTART, PlatformUI.RETURN_OK or PlatformUI.RETURN_EMERGENCY_CLOSE.
Comment 1 Stefan Lötscher CLA 2007-09-03 04:43:04 EDT
Created attachment 77572 [details]
Interactive Splash Handler Template
Comment 2 Boris Bokowski CLA 2009-11-26 16:32:44 EST
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:14:52 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.