From bbd01286649abdd6c8f7d9b64221a5db7816780b Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Mon, 7 Apr 2014 10:38:25 +0200 Subject: [PATCH] Explicitely save preferences on startup Before, the preferences were saved as a side effect of loading files in the Editor, but it seems better to explicitely save them as well (this should prevent problems later on, if the Editor class is no longer used in --verify or --upload mode). --- app/src/processing/app/Base.java | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/app/src/processing/app/Base.java b/app/src/processing/app/Base.java index e0e9858d4..b8524f5f2 100644 --- a/app/src/processing/app/Base.java +++ b/app/src/processing/app/Base.java @@ -433,6 +433,11 @@ public class Base { } } + // Save the preferences. For GUI mode, this happens in the quit + // handler, but for other modes we should also make sure to save + // them. + Preferences.save(); + switch (action) { case VERIFY: case UPLOAD: