| closing editors as a side-effect of resource deletion [message #66459] |
Sat, 07 June 2003 12:45  |
Eclipse User |
|
|
|
Encountered this problem in our plugins on WinXP and R2.1, but it seems to
be endemic:
1. Create a simple Java project with two trivial classes, Class1
and Class2.
2. Open a Java editor on each class, ensuring that Class1's editor
totally obscures Class2'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.
Any reasonable workarounds?
|
|
|
| Re: closing editors as a side-effect of resource deletion [message #66481 is a reply to message #66459] |
Sat, 07 June 2003 14:32  |
| Eclipse User |
|
|
|
Let's try that again:
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.
"John Vlissides" <vlis@us.ibm.com> wrote in message
news:bbt4rr$r34$1@rogue.oti.com...
> Encountered this problem in our plugins on WinXP and R2.1, but it seems to
> be endemic:
>
> 1. Create a simple Java project with two trivial classes, Class1
> and Class2.
>
> 2. Open a Java editor on each class, ensuring that Class1's editor
> totally obscures Class2'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.
>
> Any reasonable workarounds?
>
>
>
>
>
>
|
|
|
| Re: closing editors as a side-effect of resource deletion [message #68055 is a reply to message #66481] |
Mon, 09 June 2003 10:31 |
| Eclipse User |
|
|
|
Originally posted by: simon.ibm.oti.lab
Open a problem report againts Platform - UI
Simon :-)
"John Vlissides" <vlis@us.ibm.com> wrote in message
news:bbtb4l$tqm$1@rogue.oti.com...
> Let's try that again:
>
> 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.
>
>
> "John Vlissides" <vlis@us.ibm.com> wrote in message
> news:bbt4rr$r34$1@rogue.oti.com...
> > Encountered this problem in our plugins on WinXP and R2.1, but it seems
to
> > be endemic:
> >
> > 1. Create a simple Java project with two trivial classes, Class1
> > and Class2.
> >
> > 2. Open a Java editor on each class, ensuring that Class1's editor
> > totally obscures Class2'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.
> >
> > Any reasonable workarounds?
> >
> >
> >
> >
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02436 seconds
Home