ardour/ardour
ardour
/
ardour
13
1
Fork 0
Code Pull Requests Releases Activity

make logic for creation of startup plugin scan a little clearer 

Also, do not actually show dialog unless it's a new user or the user explicitly
asks for VST scan at startup
This commit is contained in:
Paul Davis 2019-10-25 11:55:10 -06:00
parent 12c81d9a67
commit c6b8fc78c8
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gtk2_ardour/startup_fsm.cc
View File

@ -340,7 +340,10 @@ StartupFSM::show_plugin_scan_dialog ()
that we run here, during startup, should only use the existing plugin cache (if any).
*/
plugin_scan_dialog = new PluginScanDialog ((!Config->get_discover_vst_on_start() || Profile->get_mixbus()), new_user);
const bool cache_only = (!Config->get_discover_vst_on_start() || Profile->get_mixbus());
const bool verbose = (new_user || Config->get_discover_vst_on_start());
plugin_scan_dialog = new PluginScanDialog (cache_only, verbose);
current_dialog_connection = plugin_scan_dialog->signal_response().connect (sigc::bind (sigc::mem_fun (*this, &StartupFSM::dialog_response_handler), PluginDialog));
plugin_scan_dialog->set_position (WIN_POS_CENTER);
@ -354,7 +357,6 @@ StartupFSM::show_plugin_scan_dialog ()
DEBUG_TRACE (DEBUG::GuiStartup, "plugin dialog done\n");
}
void
StartupFSM::show_new_user_dialog ()
{