Bug 38830 - closing editors as a side-effect of resource deletion
Summary: closing editors as a side-effect of resource deletion
Status: RESOLVED DUPLICATE of bug 38829
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-12 08:22 EDT by John Vlissides CLA
Modified: 2003-06-12 08:25 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Vlissides CLA 2003-06-12 08:22:59 EDT
1. Create a simple Java project with two trivial classes, Class1
    and Class2.

 2. Open a Java editor on each class, ensuring that **Class2's**
    editor totally obscures **Class1's** (i.e., don't tile the
    editors).

 3. Shut down Eclipse and restart it. Things should look pretty
    much the same as before.

 4. Choose "New Window" from the Window menu.

 5. In the new window, delete Class1 using the Package Explorer.

 6. Go to the original window. You'll notice the editor for Class1
    is still there. Click on its tab. Kablooie.

Obscured editors aren't instantiated on startup---only when they're
revealed. The error comes from FileEditorInputFactory when it tries
to reload the editor's memento information: the memento's path
points to the now-deleted resource.
Comment 1 John Vlissides CLA 2003-06-12 08:25:28 EDT

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