[Original title: Fire Event from all "Fire at Start" nodes when the "Q" key is pressed]

I'm looking for effortless comp wide revaluation whenever I need it, and think this is the most effortless way to implement the request for Vuo team. I don't want to pan around to find the Fire on Start node(s) and interact with it then go back to what i was doing.

It's an extension of my earlier request for Firing an event for a Node when user changes an input value in the Editor would be a quick shortcut for firing off execution of all the "fire at start" nodes. I find myself stoping and starting composition a lot while playing with it and this is tedious.

This is a suggestion in parallel with much broader discussion about Node execution rules/timing/generalities that's happened in a few places, most recently by George here and here on Vuo Facebook page. Also here. I don't see this request as a substitute for a more considered look at the problem, especially for new user comprehension of Vuo, just as a stop gap and augmenting it.

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

Comments

Opened for voting.

jstrecker's picture
Submitted by
Feature status:
Waiting for review by Team Vuo
»
Open for community voting

Opened for voting.

I edited the title of the feature request to leave the shortcut key open. Since there's already ⌘T to re-fire event, how about ⌘⇧T to re-fire all Fire on Start events? Any particular reason you had suggested the bare Q key? (Possible issues: doesn't follow Mac convention, and it's similar to ⌘Q for quit.)

@jstrecker If this could be

Bodysoulspirit's picture
Submitted by

@Jaymie If this could be filled in 1.3 too (if not too complicated) I guess it could already make several guys like George Toledo smile (until some deeper auto refresh method with specific time evaluation systems like QC).

With the chosen to be implemented "Fire an event from Node when an input value is changed in the Editor" adding this will allow both a node level update function as well as a top upstream chain level refresh option.

One could even imagine an option in Vuo preferences to Refire all the "Fire on start" nodes when a node value is changed !?!

reason for Q was that it's

useful design's picture
Submitted by

reason for Q was that it's easy to find on the keyboard and suggests "cue".

I think Command keys are good for things that you don't want to accidentally click (Quit/Close/Save) but i wanted it to be lighter weight solution than ⌘+⇧+"T".

its going to be a compromise between all these ideas and I'm not well placed to know the best place to refire events from but I would like it to be a single key that does the firing.

many pro apps (Adobe CC, loads of 3D apps) use single a-z keys as tool shortcuts. to me refiring events is almost a tool in itself.

Origami did a great job adding keyboard shortcuts to QC for most of their patches. 10 out of 10 Origami for that, saves so much time. especially when, unlike Vuo node library which is excellent, the QC patch library is frustratingly obtuse at search since ~v4.0.

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released