Bodysoulspirit's picture

@Bodysoulspirit

I made a donation to Vuo.
Bodysoulspirit's picture

Hi ;)

Sadly not yet, at least not with a built-in function. Loved that in QC back then, but it stopped working with QC a while back too at some macOS update.
Just created a feature request for that since I'd love that too (have to wait until the team reviews it and opens it up for voting before voting is possible) : A UI for storing / editing published ports (save prefs) for screensavers

(Not to be confused with the same request, but for exported apps instead of screensavers : A UI for storing and editing published input port values)

The only way I see now for people to change in image would be to go to the screensaver package, right-click to show package content, navigate to the image in the ressources folder and replace it with theirs I guess.

Bodysoulspirit's picture

A UI for storing / editing published ports (save prefs) for screensavers

Similar to A UI for storing and editing published input port values but for screensavers.
As Jaymie mentioned there, a dedicated Feature Request would be better.

QC equivalent: 

Published Ports did work back in the days as options

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community
Bodysoulspirit's picture
Bodysoulspirit commented on keithlang's Discussion, “💎 Some UX proposals

Beside The Feature Request page being sorted by request type, with the All Tabs sorting option, you can see all and perform a page search : Fire Event on all Fire on Start nodes when a shortcut key is pressed,

But the main request for this that was already chosen to be implemented but delayed and will remove that trouble completely is : Automatically refire nodes when input changes

Bodysoulspirit's picture
Bodysoulspirit commented on keithlang's Discussion, “💎 Some UX proposals

Hi there :)
And welcome to Vuo.

One thing I can say is some of your ideas already are listed as feature requests : Community Feature Requests. For example :
Remember Editor size and position
The composition view should have the previous size ...
You can also suggest your new ones there ;) Rename ports on sub compositions should not need a rewire, true.

Can't wait to see what you make with Vuo ;) Cheers

Bodysoulspirit's picture
Bodysoulspirit commented on Raul's Discussion, “Need help learning Vuo

You just need to think Vuo as pipes. Events stream down the chain as a push system only (for now).
This means every node that should execute should receive an event, otherwise it won't fire.

The amount of nodes it depends for what.
For some cases maybe, but for some others I don't think.

There is not yet an integrated particle system, it's on the feature request you can vote on : Particle emitter node.
It has quite many votes so I expect it to pop up sonner than later (all opened for voting requests are here : Feature Requests.)
I just uploaded a quite dirty and heavy method using stock nodes for limited particles. Of course here a lot of math is involved, and the upcoming dedicated node will make that way easier. Someone made a particle effect node a while ago, but for Vuo 1.2.8, and he did not update it for Vuo 2. Was very powerful and simple.
Link to my stock nodes particles comps : Stock Node Particles.

If you have other specific questions or need help on a specific part of a composition, ask, all questions usually are answered here.

Cheers

Pages