Bug 110418

Summary:	[WorkbenchParts] event before view is closed
Product:	[Eclipse Project] Platform	Reporter:	Marcus Koesters <info>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	eclipse, n.a.edgar
Version:	3.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Marcus Koesters

2005-09-23 07:59:50 EDT

there should be a way to inform components that a view is on it's way to be
closed.  i'm talking about something like "preShutDown()" in
ApplicationWorkbenchAdvisor.
That would enable the View to react to this event (and possibly vote against it
for  some reasons) 
yours,

Marcus

Comment 1 Kim Horne

2005-09-23 09:41:56 EDT

Under what circumstances would it be appropriate for a view to veto shutdown/closure?

Comment 2 Marcus Koesters

2005-09-23 10:13:12 EDT

(In reply to comment #1)
> Under what circumstances would it be appropriate for a view to veto
shutdown/closure?

well, the ability to veto was just one example... 
given the case that there is a view with  widgets, for example an OleFrame, on
it, and that it is nessesary to save the data in those widgets  before the view
is closed, 
trying to save the data within the dispose() method would't work bc the widgets
containig the data to save are disposed already.  

(please excuse my bad english)

yours,

marcus

Comment 3 Paul Webster

2005-09-23 10:34:34 EDT

To save information from a view as it closes, you should use
IPartListener2#partClosed(...) ... the view is being closed (i.e. there are no
other references in any other perspective) but it hasn't actually been disposed
and all of the controls should be valid.

PW

Comment 4 Paul Webster

2006-09-28 11:01:17 EDT

There are currently no plans to work on this feature.

PW

Comment 5 Denis Roy

2007-06-22 09:33:05 EDT

Changes requested on bug 193523

Comment 6 Eclipse Webmaster

2019-09-06 16:06: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.