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

Bug 362037

Summary: Restarting Apllication: EditorArea not restored probably
Product: [Eclipse Project] Platform Reporter: Daniel Stein <daniel.stein>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: emoffatt, pwebster, remy.suen
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Daniel Stein CLA 2011-10-26 04:49:21 EDT 
Build Identifier: 20110916-0149

Hi, 

I develop a tool to query a db. One Query is represented as an EditorPart-Subclass. If the programm is restarted the querys not getting restored, because the client wants this behavior. 
If multiple querys are opened and one DND a query in the editorarea so that both are shown and the user closes an restart the program the editorarea is still "splitted". 

Why get the splitted parts of the editorarea joined if the user closes the editorpart and not if the workbench closes the part?

Reproducible: Always
Comment 1 Paul Webster CLA 2011-11-02 14:08:19 EDT 
Which build did you use?  Was it 4.2 or 3.8 or 4.1.1?

It looks like bug 110684 which was fixed in 3.7, but not propagated into 4.1 (as the editor support is different).

PW
Comment 2 Daniel Stein CLA 2011-11-03 02:46:18 EDT 
(In reply to comment #1)
> Which build did you use?  Was it 4.2 or 3.8 or 4.1.1?
> 
> It looks like bug 110684 which was fixed in 3.7, but not propagated into 4.1
> (as the editor support is different).
> 
> PW

Thanks for your reply. I've targetplatforms for Eclipse 3.6.1, 3.7.0 and 3.7.1 but the problem appears with all of them. 
Does it make sense to try 3.8?
Comment 3 Daniel Stein CLA 2011-11-03 03:02:54 EDT 
I have read your patch in the bug that you mentioned and I tried the Method WorkbenchWindowAdvisor#cleanUpEditorArea() and it works for me. 

Thanks again Paul. As always your postings are a great help :-)

*** This bug has been marked as a duplicate of bug 110684 ***