cwilms-loyalist's picture

Thank-you!!!! I don't know if I ever would have noticed that! It's working now!

Bodysoulspirit's picture

Amazing Jaymie ! Hey @grahamis if you want the text size to be adjusted automatically when the window gets resized use something like this ;) (joined composition).

grahamis's picture

Hi Jaymie, Thank you so much for this, I have watched some tutorials and read the manual, slowly getting it.. One question about your patch is there a way to add test for the max characters for each individual element and trim and split if necessary? e.g. right now if someone were to accidentally enter a string with 57 characters (when limit set to 50) and no space it will not be trimmed and so expand beyond the width I'm trying to restrict the content to... does that make sense? image and patch attached.

Kewl's picture
@Kewl commented on @Kewl's Discussion, “CPU efficiency in Calculate node

Ah, OK. I've seen in other dataflow programming software (like SonicBirth) that divisions are really not ideal and turning divisions into multiplications (1/180 becoming a constant by being calculated only once) is a better approach. If Vuo is not sensitive to this, so much the better.

jstrecker's picture
jstrecker's picture
+1

Here's a composition that splits text into words and joins it back together into lines of less than or equal to 60 characters. The idea is to loop through the words and keep appending them into an accumulated text, until you find that appending one more would pass the character limit, or you reach the end of the list.

bLackburst's picture

We need something like a get item from list with expanding input drawer that blocks unselected upstream nodes.

jstrecker's picture
@jstrecker commented on @bLackburst's Question, “Push rendering optimisation

@Bodysoulspirit, I changed your comment to an answer.

Bodysoulspirit's picture
Bodysoulspirit's picture
+1

Not sure what you mean with different generators but I think a somehow related Feature is Option to temporarily disable/turn off nodes

What about using Select Output 8 if you only want one at the time and have max. 8 (can't wait for more inputs/outputs then 8 on those nodes) and connect all the filters to a Select latest 8 ? Then only 1 will be processed.

jstrecker's picture
@jstrecker commented on @Kewl's Discussion, “CPU efficiency in Calculate node

Probably the first option since it has fewer operations. But since your CPU can do billions of floating-point operations per second, you'd have to be dividing a lot of numbers for it to make a perceptible difference. Also, it takes way more CPU operations than just that little math expression to execute the node, copy the outputs to the connected inputs, etc. It's nice that CPUs are really really fast :)

jstrecker's picture
@jstrecker commented on @Bodysoulspirit's Bug Report, “Too long Tree Port Popover

Confirmed: the port popover can be really wide if the text contains tabs. Thanks for discovering this bug, @Bodysoulspirit!

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Questions and Answers

Ask a Question


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community.