Bug 249559 - [EditorMgmt] Last editor used in previous eclipse session is not activated when loading eclipse
Summary: [EditorMgmt] Last editor used in previous eclipse session is not activated wh...
Status: RESOLVED DUPLICATE of bug 188380
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M5   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2008-10-02 20:07 EDT by Nick Chiu CLA
Modified: 2009-01-14 14:03 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Chiu CLA 2008-10-02 20:07:01 EDT
Build ID: I20080617-2000

Steps To Reproduce:
1. Open a file (lets call it file A)
2. Open another file (lets call it file B), this will be our most recently used editor
3. Now put the focus on a view like Console or Error log
4. Restart eclipse
5. Notice now that the editor opened is file A but should be file B which was our most recently used editor


More information:
I have a custom application that uses the Eclipse SDK and GEF where opening files could take a very long time. What I found was this bug could open 2 files at once which is a problem for me because of performance issues when opening a large file.

I noticed in the eclipse code that it does open the most recently used editor but also the first opened editor as well if the focus was away from the editor when closing eclipse and restarting.

It looks like their is an activation ordering problem where it should be the most recently used editor and not the first opened editor. So having the focus away from the editors like to Outline or Console view and restarting eclipse will open:

1. the most recently used editor and
2. the first editor opened in the previous session
Comment 1 Kevin McGuire CLA 2008-10-06 12:16:25 EDT
Verified in M2.
Yes opening both editors is a clear performance glitch, aside from the obvious "put things back the way I left them" tab ordering.
Comment 2 Oleg Besedin CLA 2009-01-14 14:03:54 EST
This looks like a part of the problem described in the bug 188380.


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