Skip to content
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

Closed
Trobinou opened this issue Oct 1, 2023 · 5 comments
Closed

Comments

@Trobinou
Copy link

Trobinou commented Oct 1, 2023

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?

@rgthree
Copy link
Owner

rgthree commented Oct 2, 2023

Hmm.. there's only one actual "button" on the Fast Actions Button node and that's what actually runs the actions. Is that what you mean by "validate" ?

So, taking the following example, it has one button ("Action!" and three combos to select which actions to run).
fast_actions_button

  • Clicking that "Action!" button will run the three actions which, in this case, are:
    • Resetting the connected Seed node to randomize
    • Setting all toggles on the connected Fast Muter to "mute"
    • And then queuing the prompt to run

Perhaps I'm misunderstanding, but the button surely needs to exist to click it :)

@Trobinou
Copy link
Author

Trobinou commented Oct 2, 2023

The choice of the term 'validate' was not appropriate, but indeed, it is about clicking the 'Action!' button to execute the selected actions.
What I meant is, would it not be possible to choose the desired option, for example, for the 'seed' in your example, between 'Fixed-increment-decrement-randomize,' and have the choice executed without pressing the 'Action!' button?

@aegis72
Copy link

aegis72 commented Oct 23, 2023

I think the intention of this node might be as a macro…ie, one button that sets the workflow in a specific state.
In my workflow AegisFlow, I’d connect a huge host of nodes that set various parameters and enabled some nodes while muting others…say, a single action button that eliminates all nodes from executing except the most basic setup for testing and experimentation.

@Trobinou Trobinou reopened this Oct 23, 2023
@Trobinou
Copy link
Author

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 👌
I'm closing this request as it seems to me that there's no reason for it.

@aegis72
Copy link

aegis72 commented Oct 23, 2023

EDIT: Confused this with another post :)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants