Force press if already pressed option on Button action: Trigger press if variable meets condition

[Jbautista13]

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

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

Is there an existing issue for this?

• I have searched the existing issues

Describe the feature

Both the

Button: Trigger press and Button: Trigger press and release if expression is true

actions feature a Force press if already pressed option, useful for running a buttons actions again with new parameters, or running actions in a different step without physically releasing the button and pressing it again. This option is incredibly useful in many instances.

There also exist two other press actions,

Button: Trigger press if variable meets condition and Button: Trigger press and release if variable meets condition

these two feature the built in variable comparison check, and only if the comparison is found true is the button press triggered.

The one issue with these two actions is that they don't feature the Force press if already pressed option. Is it possible to add this option to the if variable meets condition variant of these actions? It's a bit confusing that it's an option in two of the existing actions, including an expression boolean check, but not in the variable boolean checks.

As for why we can't simply use the existing Button: Trigger press and release if expression is true there are instances when you only want to trigger a press and not a release which is why the Button: Trigger press if variable meets condition needs to be used.

Usecases

There are buttons which use force a Button: Trigger press action in order to on condition run a seperate set of actions in a different step previously decided upon using a

Button: Set current step if variable meets condition or Button: Set current step if expression is true action

there are instances when you may in fact have decided not to switch to a new step and instead stay on the current one, but if you trigger a press in this instance a loop may be created and the stack overflows, usually this results in a slowdown for a couple seconds which can be detrimental during an event. This can be resolved by adding a blank step to any buttons that require this, and instead of staying on the current step moving to the blank step which simply sends you back to the step you wanted to stay on from the beginning.