add Stripable analogs for Route signals and methods in ControlProtocol
These will go away once all surfaces have migrated to Stripables
This commit is contained in:
@@ -84,12 +84,19 @@ class LIBCONTROLCP_API ControlProtocol : public PBD::Stateful, public PBD::Scope
|
||||
static PBD::Signal1<void,uint64_t> RemoveRouteFromSelection;
|
||||
static PBD::Signal0<void> ClearRouteSelection;
|
||||
|
||||
static PBD::Signal1<void,uint64_t> AddStripableToSelection;
|
||||
static PBD::Signal1<void,uint64_t> SetStripableSelection;
|
||||
static PBD::Signal1<void,uint64_t> ToggleStripableSelection;
|
||||
static PBD::Signal1<void,uint64_t> RemoveStripableFromSelection;
|
||||
static PBD::Signal0<void> ClearStripableSelection;
|
||||
|
||||
/* signals that one UI (e.g. the GUI) can emit to get all other UI's to
|
||||
respond. Typically this will always be GUI->"others" - the GUI pays
|
||||
no attention to these signals.
|
||||
*/
|
||||
|
||||
static PBD::Signal1<void,RouteNotificationListPtr> TrackSelectionChanged;
|
||||
static PBD::Signal1<void,StripableNotificationListPtr> StripableSelectionChanged;
|
||||
|
||||
/* the model here is as follows:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user