Bug 88297 - [ViewMgmt] unattach one or all views from window
Summary: [ViewMgmt] unattach one or all views from window
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-03-17 03:46 EST by Thomas Richter CLA
Modified: 2019-09-06 16:04 EDT (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 Thomas Richter CLA 2005-03-17 03:46:34 EST
Hi,
I need a button to unattach all views from window. I can unattach one
view with the mouse from the window. But I have no starting point
where to call a function.
Comment 1 Nick Edgar CLA 2005-03-17 16:33:33 EST
Sorry, is this an API request or a UI enhancement request?
Comment 2 Thomas Richter CLA 2005-03-18 02:44:29 EST
(In reply to comment #1)
> Sorry, is this an API request or a UI enhancement request?
> 
Jean-Michel Lemieux wrote in
news://news.eclipse.org:119/d1assh$34t$1@www.eclipse.org
There is no API to do so. Log an enhancement request against Platform UI.

I want to do this:

for all v in views do
   v.deatach()
od
Comment 3 Nick Edgar CLA 2006-03-15 13:28:03 EST
Reassigning bugs in component areas that are changing ownership.
Comment 4 Remy Suen CLA 2008-02-15 10:25:00 EST
Would it make more sense to abstract this out further at the WorkbenchPart level instead of the ViewPart level?
Comment 5 Boris Bokowski CLA 2008-02-15 10:56:03 EST
I think the request was to add API for programmatically detaching a view. Editors cannot be detached, at least not currently.
Comment 6 Boris Bokowski CLA 2009-11-11 17:32:39 EST
Remy is now responsible for watching the [ViewMgmt] category.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:04:44 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.