Community
Participate
Working Groups
- new file B.txt - change B.txt in the filesystem - open B.txt in Eclipse - it gives an error dialog: "Problems Opening Editor" / "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 necessary. There's only one content which can be seen in the editor. It could just do a refresh for you and open it. NOTES: NE (5/25/01 1:25:37 PM) Are there any disadvantages to just doing a refresh? Need to check with a Core person. DS (5/29/01 8:43:27 PM) I will write an operation to do a refresh ( with user confirmation ) if the resource has changed. This operation can be reused throughout desktop in open editor, copy, move, delete, etc. Out of sync states to deal with = modify, delete DS (5/29/01 9:24:37 PM) According to Rodrigo there is no way to see if a file is out of sync. Perhaps it would involve doing everything a localRefresh does, but without doing the localRefresh. KH (5/30/2001 2:50:50 PM) Local refresh will cause builders to run. We should NOT do this for free.
PRODUCT VERSION: 110 JDK
Moving to Core for comment
Stale PR. UI now does a local refresh. This seems fine as long as a progress dialog is shown. See http://dev.eclipse.org/bugs/show_bug.cgi?id=6091