when Session emits RouteAdded, each handler (editor, mixer, trigger pages etc) will execute their callbacks in order. But Editor::add_routes() selects the routes too, which triggers a PresentationInfo::Change signal. This is received by e.g. the Mixer before it has even found out about the newly added stripables. This in turn leads to severe confusion regarding the state of the selection in the mixer, and potentially elsewhere. So, just add a PresentationInfo::ChangeSuspender for the scope of the RouteAdde signal emission |
||
---|---|---|
doc | ||
gtk2_ardour | ||
headless | ||
libs | ||
luasession | ||
msvc_extra_headers | ||
MSVCardour3 | ||
MSVCMixbus3 | ||
MSVCvst_scan | ||
session_utils | ||
share | ||
tools | ||
.dir-locals.el | ||
.gitattributes | ||
.gitignore | ||
ardour.1 | ||
COPYING | ||
nutempo-todo | ||
PACKAGER_README | ||
README | ||
README-GITHUB.txt | ||
system_config | ||
TRANSLATORS | ||
waf | ||
wscript |
Please see the Ardour web site at https://ardour.org/ for all documentation.. For information on building ardour: https://ardour.org/development.html