Community
Participate
Working Groups
When editing a Java file, if auto-generation changes the content on disk, the captive "File chnaged" pop-up appears. Good. The Pop-up is now clearly worded; big improvement. It offers "Replace" / "Do not replace" options. However if the auto-generation takes place under the debugger, so that a file deletion occurs but recreation does not, the different "File Not Accessible" pop-up appears offering "Save" or "Close". There is no go away and leave me alone option. "Save" saves the edits. ok "Close" closes the editor trashing the edits. consistent but misleading unless the full-text is read. "Close" is ambiguously close-editor/close-dialog. Please re-label as "Close Editor". Why does the window frame "X" close the dialog and editor, and so also trash the edits? Surely "X" should be "Close Dialog" allowing the in-memory edits to continue, possibly copying experimental content back to the auto-generation template. Similarly if the "Save" button was chosen giving the "Save As" dialog, "Cancel" then reverts to the "File Not Accessible" dialog rather than allowing the editor to resume.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Cannot be stale until triaged by a relevant committer.
