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

Bug 97953

Summary:	[ViewMgmt] Standalone views lose their standalone property after moving
Product:	[Eclipse Project] Platform	Reporter:	Boris Bokowski <bokowski>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	Keywords:	helpwanted
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Boris Bokowski

2005-06-01 14:51:54 EDT

A standalone view which is moveable loses its standalone property when you move 
it.

Comment 1 Boris Bokowski

2005-06-01 14:56:40 EDT

This only applies to standalone views with a title.

Comment 2 Nick Edgar

2005-06-01 17:15:13 EDT

Can you provide more concrete steps?

Comment 3 Boris Bokowski

2005-06-01 17:28:49 EDT

Sure -

Check out the RCP Browser example. Change the BrowserPerspectiveFactory to add 
a standalone view instead of a normal view, i.e. change the first line to

layout.addStandaloneView(IBrowserConstants.BROWSER_VIEW_ID, true, 
IPageLayout.RIGHT, .25f, IPageLayout.ID_EDITOR_AREA);

Then start the browser example, point the first browser view to 
www.standalone.org <g> to know that this is the standalone one. Hit Ctrl-T to 
open a second browser view.

Note that you cannot drag-and-drop the second view on top of the standalone 
view.

Now move the standalone view to the right of the other view. After this, you 
can drag-and-drop the second view on top of the standalone view.

Comment 4 Nick Edgar

2006-03-15 13:28:04 EST

Reassigning bugs in component areas that are changing ownership.

Comment 5 Boris Bokowski

2009-11-11 17:32:10 EST

Remy is now responsible for watching the [ViewMgmt] category.

Comment 6 Eclipse Genie

2019-08-30 13:01:50 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.