You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature
Ability to copy buttons and change which instance they affect without changing or reselecting the action. Sub-request, add ability to copy an action within a button (and then select the instance separate from the action.)
Usecases
I find I do a lot of work where I am copying buttons that all have the same action and/or action parameters but want to control different devices (instances) or I'm copying actions on a button to control the same function on multiple devices (instances.) As examples, copying a button which starts a cue playing to another button to start that same cue on a backup device, or in the multiple actions on a single button front starting a record across multiple record decks with a single button. If done as I'm envisioning the implementation, the action list could/would additionally be limited by the selected instance giving an added bonus to usability. With even a modest number of devices the current method of having to re-add all the actions is not only tedious but the list of actions one needs to search through can get quite large.
The text was updated successfully, but these errors were encountered:
Describe the feature
Ability to copy buttons and change which instance they affect without changing or reselecting the action. Sub-request, add ability to copy an action within a button (and then select the instance separate from the action.)
Usecases
I find I do a lot of work where I am copying buttons that all have the same action and/or action parameters but want to control different devices (instances) or I'm copying actions on a button to control the same function on multiple devices (instances.) As examples, copying a button which starts a cue playing to another button to start that same cue on a backup device, or in the multiple actions on a single button front starting a record across multiple record decks with a single button. If done as I'm envisioning the implementation, the action list could/would additionally be limited by the selected instance giving an added bonus to usability. With even a modest number of devices the current method of having to re-add all the actions is not only tedious but the list of actions one needs to search through can get quite large.
The text was updated successfully, but these errors were encountered: