In AVLite 0.5.3, load_stack_settings(profile) imports packages listed under c69_apps.c62_community_plugins, but does not call load_community_plugin_setting() for them. Community settings under plugins. are loaded by the Settings GUI, but are not reliably applied during initial visualizer startup, headless startup, or hot reload.
Expected:
After importing each registered community plugin, AVLite should load its PluginSettings singleton from the selected profile before stack components are constructed.
Possible fix:
In avlite/c60_apps/c62_factory.py, import load_community_plugin_setting from c63_plugins, then call it immediately after importing each community plugin:
for name, stored in AppSettings.c62_community_plugins.items():
path = PluginPaths.resolve(name, stored)
if path.is_dir():
import_plugin_modules(str(path), pkg_name=name)
load_community_plugin_setting(
name,
stored,
profile=profile,
)
In AVLite 0.5.3, load_stack_settings(profile) imports packages listed under c69_apps.c62_community_plugins, but does not call load_community_plugin_setting() for them. Community settings under plugins. are loaded by the Settings GUI, but are not reliably applied during initial visualizer startup, headless startup, or hot reload.
Expected:
After importing each registered community plugin, AVLite should load its PluginSettings singleton from the selected profile before stack components are constructed.
Possible fix:
In avlite/c60_apps/c62_factory.py, import load_community_plugin_setting from c63_plugins, then call it immediately after importing each community plugin: