Bug 145833 - [View Mgmt] Views cannot be thown away at the end of a session
Summary: [View Mgmt] Views cannot be thown away at the end of a session
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-07 14:28 EDT by brian fjeldstad CLA
Modified: 2019-09-06 16:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brian fjeldstad CLA 2006-06-07 14:28:00 EDT
There seems to be no way to make a view non-persistent.  

I have users that want to create multiple graphs in separate views from within our eclipse plugin.  To accomplish that, I use the multiple-instance views.  That works great.

However, when a graph has been created, it only exists for the current session.  So, persisting the view doesn't make sense.  It seems like this wouldn't be the only use case where a view should not be required to be persistent.
Comment 1 brian fjeldstad CLA 2006-06-07 17:37:55 EDT
There seems to be a workaround in 3.2 via the IWorkbench.addWorkbenchListener that allows a plugin to listen for a pre-shutdown method that you can then go about hiding views you don't want to persist.

Is there an equivalent for pre-3.2?
Comment 2 Boris Bokowski CLA 2006-06-08 11:03:10 EDT
Sorry, no, there is no way to do this pre 3.2 if you don't control the application. In an RCP application, you can use WorkbenchAdvisor.preShutdown(), which is @since 3.0.
Comment 3 Remy Suen CLA 2009-11-29 09:47:04 EST
Brian, if you've migrated your project to Eclipse 3.4, you can try the new 'restorable' attribute that was added to the views extension point, see bug 215797.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:08:23 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.