Community
Participate
Working Groups
- new file B.txt - modify it in the editor, but don't save - change B.txt in the filesystem - save B.txt in Eclipse - it gives an error dialog: "Save problems" / "Internal Error: Reason: File has changed since last synchronization." A: This case will happen often B: What is synchronization? We don't use that term in the UI anymore. C: It doesn't show how to rectify the situation. How is a novice user supposed to know to do a refresh local? D: It's not an internal error. Eclipse didn't fail (it is, however, failing to meet the user's expectations.) E: It throws away the changes made in Eclipse! This is really bad, as it loses the user's work. It should notify that the file has changed since it was opened, and offer to: 1 - save anyway, overwriting other changes 2 - abandon changes made in editor 3 - compare differences and merge For 1 and 2, it should not really lose the other contents, but put them in the recycle bin or local history so they can be recovered later if the user makes the wrong choice here, or needs them later. NOTES: NE (5/25/01 1:35:04 PM) Similar behaviour if file has been deleted in filesystem. The editor contents are lost. In this case, it should just save the editor contents.
PRODUCT VERSION: 110 JDK
Moving to Core for comment
Stale PR, this seems to be fixed in 2002-01-15. It prompts the user with a more friendly message and allows either saving or cancelling. No work is lost if the user cancels. Closing.
