rstarkov
Addon Developer
A couple of addons I work on need to store some settings that are independent of the current scenario. For example, WindowTack stores the window positions at various resolutions. ReFuelMFD will store a couple of settings related to whether refuelling is allowed without being docked.
Where should these settings files go?
/Config - probably not
/Config/MFD - looks reasonable for an MFD but not so much for WindowTack
/Config/Modules - looks fine...
...except that the documentation states that only ROOT and SCENARIOS are guaranteed to be writable, thus precluding CONFIG completely.
So should I litter ROOT or SCENARIOS, or make my addons incompatible with mostly-read-only installations?...
P.S. While searching the forums for an answer, I found a thread titled something like "Hardest thing about developing addons". For me, the hardest thing is dealing with Orbiter's "organic" growth, i.e. the absence of an overarching upfront design that foresees and accommodates boring details like this one...
Where should these settings files go?
/Config - probably not
/Config/MFD - looks reasonable for an MFD but not so much for WindowTack
/Config/Modules - looks fine...
...except that the documentation states that only ROOT and SCENARIOS are guaranteed to be writable, thus precluding CONFIG completely.
So should I litter ROOT or SCENARIOS, or make my addons incompatible with mostly-read-only installations?...
P.S. While searching the forums for an answer, I found a thread titled something like "Hardest thing about developing addons". For me, the hardest thing is dealing with Orbiter's "organic" growth, i.e. the absence of an overarching upfront design that foresees and accommodates boring details like this one...
