1
0
mirror of https://github.com/cookiengineer/audacity synced 2025-07-05 06:59:07 +02:00
martynshaw99 91da5e2354 This to make no modules 'special', reverting what was done for Audacity 2.0.2. We ask each time about each module to see if the user want to load it.
Anything to do with modules and prefs is currently under EXPERIMENTAL_MODULE_PREFS and turned off.
We never load 'out of date' modules (but do allow modules to interrogate the current prefs and 'pretend' they are that version.  The 'Aurora' plug-ins do that).
If a module is 'out of date' we provide the name in a user-facing message and actual location in the log, just in case the user has a number of versions in different places (untested).
We currently don't remember the users preference for loading each module, but could extend this.  We would need an extra button in the ShowMultiDialog of ModuleManager::Initialize and then store the preferences in prefs.  That would need a more sophisticated entry in prefs->Modules to enable a user to change their decisions.
2013-06-16 23:31:32 +00:00
..