Community
Participate
Working Groups
If the user selects to run a release/catchup on files that are modified, but not saved yet, should we prompt the user that the files should be saved first or help him save them? NOTES: KM (5/23/01 10:23:24 PM) Also there is an existing PR suggesting we should refresh from local too. KM (05/27/01 3:19:55 PM) Future. This is equivalent to prompting that they save before run/debug (which we don't).
However the refactoring wizards prompt you to save changes.
PRODUCT VERSION: 0.111 JDK
*** Bug 6099 has been marked as a duplicate of this bug. ***
Such prompting now appears in numerous places in the eclipse, except us.
*** Bug 14116 has been marked as a duplicate of this bug. ***
Pretty much all we need. We might be able to get away with just saving the editors on the active page, but I doubt it. protected void saveAllEditors(final boolean confirm) { Display.getDefault().syncExec(new Runnable() { public void run() { IWorkbenchWindow[] windows = PlatformUI.getWorkbench().getWorkbenchWindows(); for (int i = 0; i < windows.length; i++) { IWorkbenchPage[] pages = windows [i].getPages(); for (int j = 0; j < pages.length; j++) { pages[j].saveAllEditors (confirm); } } } }); }
Fixed. A CVS preference controls the save behavior (never, auto, prompt) for dirty editors prior to running CVS actions.