Bug 2398 - Strange behaviour deleting a project with unsaved changes (1GEYHSF)
Summary: Strange behaviour deleting a project with unsaved changes (1GEYHSF)
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2001-10-10 22:35 EDT by Kevin Haaland CLA
Modified: 2002-04-03 16:25 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Haaland CLA 2001-10-10 22:35:39 EDT
1) create a new generic project 'MyProject' in the Navigator
2) create a new file 'MyFile' in the project  (a text editor will pop up)
3) edit the file but don't save it
4) select 'MyFile' and delete it

At this point the file is deleted, the editor is still open however.
I am not sure if this is the expected behaviour but I would think the user would assume
changes would be lost when deleting the file so closing the editor(s) with changes
should be ok.  An editor without changes is closed properly when its file is deleted.

Follow up problem:
5) close or delete ALL your projects
6) close the open editor of 'MyFile

You will be prompted to save changes, if you click 'yes' you will not have any projects available
to save the file to so you will have to cancel and lose changes.  This problem would not exist if
editors were closed properly - the user shouldn't be asked to save changes to a 'deleted' file.

NOTES:
Comment 1 DJ Houghton CLA 2001-10-29 18:25:31 EST
PRODUCT VERSION:
119-jdk

Comment 2 Nick Edgar CLA 2002-01-22 22:15:31 EST
See also bug 2399
Comment 3 Nick Edgar CLA 2002-04-03 16:25:24 EST
It now prompts to save changes when editor is activated.