Button Properties as Internal Variables

[DrEVILish]

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

• [x] I believe this to be a feature for companion, not a module

Is there an existing issue for this?

• [x] I have searched the existing issues

Describe the feature

Apologies if this is duplicate, I did search.

I would like the ability to access a Buttons properties from a different page/button. e.g. $(9/0/2:state) - would return the integer of the current state of a button $(9/0/2:originalName) - would return the original Button text string (as set on the edit button page) $(9/0/2:currentName) - would return the current Button text string (after feedback manipulations)

Recently had a situation where programming this in would have saved a fair bit of custom-variable setup assignments and recalls, as just setting the Button "State" would have been enough to keep track of the part of the program, and the button was part of the action as well.

Having Original name + something added by a feedback. Would greatly reduce the amount of copy and paste or Custom-Variable assignments.

Usecases

No response

[MikeDFWM]

For my use, the ability to access a variable on whether or not a button is currently executing actions (the same thing powering the green play button) would be immensely helpful for specific feedbacks, etc.

I know button-specific variables have been discussed quite a bit, but access to current state in regards to executing/not executing isn't something I've seen come up.