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.

Author: matthijskooijman

app/src/processing/app/Base.java

@@ -449,6 +449,10 @@ public Base(String[] args) throws Exception {
         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) {