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

Bug 82801

Summary: [Intro] Problem with not bringing up intro if workbench state not saved
Product: [Eclipse Project] Platform Reporter: Nick Edgar <n.a.edgar>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 Keywords: helpwanted
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard: stalebug

Description Nick Edgar CLA 2005-01-13 17:22:03 EST
build I20040104

Looking at the code for openIntro, although it talks about checking the
saveAndRestore flag, it doesn't.  So the following could happen:
- new workbench
- show intro pref defaults to true
- intro is opened, and pref is set to false
- user exits (workbench state not saved)
- start workbench
- new window is opened 
- intro is not shown

It's probably worth decoupling the pref and the "already shown intro" flag.
The pref will let apps customize whether intro is shown at all, and the
workbench will keep the shown flag separately as workbench state.
If the workbench state is not saved, then only the pref will be considered next
time.
Comment 1 Susan McCourt CLA 2009-07-09 19:09:29 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:58 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.
Comment 3 Eclipse Genie CLA 2021-11-27 08:41:44 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.