Launcher sets —no-default-config automatically.

[flightgear.git] / src / Main / options.hxx

diff --git a/src/Main/options.hxx b/src/Main/options.hxx
index 60a59d971a2e0b5e81c2b9437ff364c4771e38ae..e680f26d1ac5f85a961c64d8f09a6df34d81d7e1 100644 (file)
--- a/src/Main/options.hxx
+++ b/src/Main/options.hxx
@@ -128,13 +128,19 @@ public:
   /**
    * should defualt configuration files be loaded and processed or not?
    * There's many configuration files we have historically read by default
-   * on startup - preferences.xml, fgfs.rc in various places and so on.
+   * on startup - fgfs.rc in various places and so on.
    * --no-default-config allows this behaviour to be changed, so only
-   * expicitly listed files are read - this is useful for testing. Expose
+   * expicitly listed files are read Expose
    * the value of the option here.
    */
   bool shouldLoadDefaultConfig() const;
 
+    /**
+     * when using the built-in launcher, we disable the default config files.
+     * explicitly loaded confg files are still permitted.
+     */
+    void setShouldLoadDefaultConfig(bool load);
+
   /**
    * check if the arguments array contains a particular string (with a '--' or
    * '-' prefix).