Button specific variables to help build buttons faster #3406
thumperdisney
started this conversation in
Ideas
Replies: 1 comment
-
This is partly solved by #3314 (which will likely be in 4.1) and #2345 which I don't think has been started on yet |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is definitely a companion feature request rather than any individual module request. Also, if this is already possible I apologize for my inability to figure it out and would like some help as it's been an annoyance to me for 3 years and I haven't found a solution available.
When I am building a new page or pages in Companion I often find that I'm building many buttons that are essentially the same so I will build 1 button and then copy and edit it to build the next and repeat that process until I have all the buttons I need for controlling a particular device. I would really like it if the button had a "variable" field built right into it located just above the button text string where you could enter a number that could be used in the all actions and feedbacks of that button, if it could also be used in the Button text string that would be nice also but not as necessary.
This would make it so when I copy a button the only two things I need to change are the button text string and that variable and the actions and feedbacks would change along with it. If the button text string can use the variable also then may times I'd be able to use that to cause it to be dynamic as well and only have to change the one spot.
I've seen this suggestion before using a button number as the local variable so that the builder can build a button once and have it be dynamic according to where they copy and paste the button on the streamdeck but I don't want to be locked into button 1 on the streamdeck associating with input 1 on the controlled device and button 2 associated to input 2; a variable on the button itself would solve that.
This variable wouldn't need to be polled by other buttons or listed in the overall variables list or anything like that. Maybe others will say that it should but I don't personally see any reason that would be helpful and if needed a person could build custom variables and use them instead.
Beta Was this translation helpful? Give feedback.
All reactions