Description Jill Daly 2012-01-05 08:56:09 EST

Build Identifier: Version: Helios Service Release 1    Build Id: 20100917-0705

This issue is specifically regarding a re-launch of a previously maximised application. The application does not remember/restore the application to a maximised state. 

However, if the application was not maximised, then on being re-launched, the application window remembers/restores the window to the previous re-size and location. 

In each of my tests, if the application was maximised before it was exited, it was not maximised when it was opened again. 

I did different instances where I have edited the contents of the application after being maximised, and then exited the app. 

I exited the app using File -> Exit, as well as clicking the x in the title bar. 


Notes: 
======
- the ApplicationWorkbenchAdvisor class in our app has the saveAndRestore call:

   @Override
   public void initialize(IWorkbenchConfigurer configurer)
   {
      super.initialize(configurer);
      configurer.setSaveAndRestore(true);
   }

- This issue occurs in Eclipse Helios SR1 Packages (v 3.6.1)
  (I also tested 3.7, and the issue also occurs in this version)

- This issue DID NOT occur in a previous release (3.4.x)



Research:
=========
In order to test/reproduce this issue I decided to create a basic hello world app to see if it occurred there too. I created Lars Vogel's Hello RCP
app, and added the configurer.setSaveAndRestore(true) as described in 
his tutorial. I was able to reproduce the issue with this hello world rcp app. 
http://www.vogella.de/articles/EclipseRCP/article.html#tips_userlayout


I have read the API Reference (for 3.7) for WorkBenchAdvisor, and can't
find any suggestions for this issue:
http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fapi%2Findex.html


I have read through Eclipse bugs to see if this has already been logged.
I've found bugs in this area, but nothing that addresses the maximise 
issue specifically:
https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=setSaveAndRestore%28true%29
https://bugs.eclipse.org/bugs/show_bug.cgi?id=313883


I have seen Lars Vogel's blog post about a command line flag for e4, 
but I don't think it's relevant for a 3.6 issue:
http://www.vogella.de/blog/2010/10/17/saveandrestore-e4/

Reproducible: Always

Steps to Reproduce:
1. Launch RCP application 
2. Maximise Window
3. Close application
4. Re-launch same application
5. Window is not maximised