search

bitfocus / companion

Bitfocus Companion enables the reasonably priced Elgato Streamdeck and other controllers to be a professional shotbox surface for an increasing amount of different presentation switchers, video playback software and broadcast equipment.
http://bitfocus.io/companion
Other
1.46k stars 489 forks source link

Trigger on buttons #2892

Open whopkinscom opened 3 weeks ago

whopkinscom commented 3 weeks ago

Is this a feature relevant to companion itself, and not a module?

Is there an existing issue for this?

Describe the feature

A trigger associated directly with a button. For example I have a "Camera/input enabled/disabled" configuration page. If I enable an input then the page where I do my ATEM switching has buttons put to the appropriate step for doing something or nothing. As I add additional pages with switching buttons, I have to go to the enable/disable triggers for each input and add the buttons on the new pages. It struck me that if a button had a trtigger tab, it would make keeping track of all this much easier, especially as the actions that utilise "This button" would make far more sense. It would effectively be a shortcut way to access existing triggers and shouldn't require too much reconfiguring to implement.

Usecases

For example I have a "Camera/input enabled/disabled" configuration page. If I enable an input then the page where I do my ATEM switching has buttons put to the appropriate step for doing something or nothing. As I add additional pages with switching buttons, I have to go to the enable/disable triggers for each input and add the buttons on the new pages.

michaelbaae commented 2 weeks ago

Could you have a main switching page and have all the new switching pages trigger buttons on the main switching page? Then setting a camera input button step on the main page to nothing would make all the other buttons follow.

whopkinscom commented 2 weeks ago

Yes, in that instance that would help but I believe the use case goes easy beyond this. It would keep all of the "code" together where a trigger was directly associated with a button, would make copying buttons along with their associated triggers just nicer. Overall just a bit more OO.