It's very simple to create a callback at the app level (i.e. in our case, qcgui), that links the sliders.
This would really simplify mne_visualizer, (especially its callback) which we want to split off into its own project at some point, because then in any given instance of MNEVIsualizer, a channel/time slider would only ever be an input for it's own graph.
mea culpa on the current design where we made the
mne_visualizer
module handle slider sharing/syncing between different instances of the class.https://github.com/lina-usc/pylossless/blob/4c3ae7108da82a1985f4548394d472dbbfb7db37/pylossless/dash/mne_visualizer.py#L282-L291
It's very simple to create a callback at the app level (i.e. in our case,
qcgui
), that links the sliders.This would really simplify
mne_visualizer
, (especially its callback) which we want to split off into its own project at some point, because then in any given instance ofMNEVIsualizer
, a channel/time slider would only ever be aninput
for it's own graph.I'll open a PR.