-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consideration - Fast Actions Button - Is the 'action' button necessary? #33
Comments
The choice of the term 'validate' was not appropriate, but indeed, it is about clicking the 'Action!' button to execute the selected actions. |
I think the intention of this node might be as a macro…ie, one button that sets the workflow in a specific state. |
You're right, especially as the pack is rich enough in nodes to do as I wish: [Mute / Bypass Relay] + [Fast Muter] or [Fast Bypasser] gives me complete satisfaction 👌 |
EDIT: Confused this with another post :) |
Is this button really necessary to confirm the choices?
Indeed, I noticed that when the workflow loads, I have to start by pressing this button to validate the displayed choices. If I don't do that, the actions don't proceed as displayed.
Furthermore, I often forget (my fault) to confirm my choices because, for me, it is logical that when I see 'enable,' for example, the action should be triggered without the need to validate it.
So my question is: could we do without this button?
The text was updated successfully, but these errors were encountered: