From 7cb99ad7b852640d9ff31e046f4954440746da7e Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Mon, 7 Apr 2014 11:51:09 +0200 Subject: [PATCH] Ensure --verbose is never saved to preferences.txt Previously, --verbose would be processed after the preferences were saved, which should usually mean that it should never influence the saved preferences. However, if for whatever reason Preferences.save() would be called later, the verbosity preferences would still be messed up. Since we now have a Preferences.setDoSave() method, we can make sure that these verbosity preferences (and any other preferences that are changed after the build started) are never saved. --- app/src/processing/app/Base.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/app/src/processing/app/Base.java b/app/src/processing/app/Base.java index 4969bd2a5..e3fe238ca 100644 --- a/app/src/processing/app/Base.java +++ b/app/src/processing/app/Base.java @@ -449,6 +449,10 @@ public class Base { Preferences.set("build.verbose", "" + doVerboseBuild); Preferences.set("upload.verbose", "" + doVerboseUpload); + // Make sure these verbosity preferences are only for the + // current session + Preferences.setDoSave(false); + Editor editor = editors.get(0); if (action == ACTION.UPLOAD) {