Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368959 - Intro left empty in a perspective with fixed layout
Summary: Intro left empty in a perspective with fixed layout
Status: CLOSED DUPLICATE of bug 295398
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 08:19 EST by Mathias Markert CLA
Modified: 2012-01-18 11:22 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Markert CLA 2012-01-18 08:19:46 EST
Build Identifier: 20110916-0149

The content of an intro depends on the view being zoomed, in order to be shown. As a view cannot be zoomed, when the perspecive layout is fixed ( IPageLayout.setFixed(true) ), the content is not loaded.

This is due to WorkbenchIntroManager.setIntroStandby(IIntroPart part, boolean standby):
The content of the intro is loaded because of the call:
viewIntroAdapterPart.getSite().getPage().toggleZoom(		pane.getPartReference());
This call fails in an early state, when the perspective's layout is fixed and the view cannot be zoomed. Furthermore, the content of the intro is not loaded.

Reproducible: Always

Steps to Reproduce:
1. Create an intro using CustomizableIntroPart using html 
(as described in Platform Plug-in Developer Guide > Programmer's Guide > User assistance support > Welcome > Using the CustomizableIntroPart).
2. Set the layout of a perspective as fixed:
  public void createInitialLayout( IPageLayout layout )
  {
    ...
    layout.setFixed( true );
    ...
  }
3. Start the RCP-application and start the intro during startup or by the command handler: org.eclipse.ui.help.quickStartAction)
Comment 1 Mathias Markert CLA 2012-01-18 11:22:22 EST

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