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

Bug 86742

Summary:	[RCP][Perspectives] Visible placeholder folder with invisible views at startup
Product:	[Eclipse Project] Platform	Reporter:	Marco Maccaferri <macca>
Component:	UI	Assignee:	Daniel Rolka <daniel.rolka>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel.rolka
Version:	3.0.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Marco Maccaferri

2005-02-26 03:05:00 EST

In the WorkbenchAdvisor class a placeholder folder is created. The folder is
initially empty.
In another plugin I have a view that is targeting the placeholder folder created
in the WorkbenchAdvisor. This view is initially not visible (visible=false).
When the application is started for the first time (i.e. without a valid
workspace) the placeholder folder is visible and is empty. The placeholder
folder is not visible at the subsequent program starts. Removing the plugin
makes the placeholder folder invisible even when the workspace is first created.
The correct behaviour should be that the placeholder folder is not visible when
the workspace is first created.
This problem seems to be present even in 3.1M5a.

Comment 1 Nick Edgar

2006-03-15 11:24:27 EST

Reassigning bugs in component areas that are changing ownership.

Comment 2 Marco Maccaferri

2008-02-29 09:35:47 EST

Any hope to see this fixed in 3.4 ?

Comment 3 Boris Bokowski

2009-11-26 16:14:34 EST

Prakash is now responsible for watching bugs in the [RCP] component area.

Comment 4 Marco Maccaferri

2011-05-07 04:12:48 EDT

Any chance to get a fix for 3.7 ?

Comment 5 Prakash Rangaraj

2011-05-09 01:20:20 EDT

(In reply to comment #4)
> Any chance to get a fix for 3.7 ?

    No. We are in the RC cycles and only critical bugs will get fixed

Comment 6 Eclipse Genie

2019-05-17 16:30:20 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.

--
The automated Eclipse Genie.