useful design's picture

Alastair (@usefuldesign)


  • Vuo Founder


2 years ago
useful design's picture
Alastair commented on Bodysoulspirit's Feature Request, “Export as OSX Screensavers

Slightly OT, happy to move to a new thread, but for my Screensaver I need to be able to startup an AppleScript that gets current song and next song info from iTunes… I can do it in QC can I do this in Vuo in anyway with an exported screensaver?

I think QC screensavers don't work with macOS anymore do they?

useful design's picture
Alastair commented on Bodysoulspirit's Feature Request, “Export as OSX Screensavers

Is there a way to access the votes that choose FR's got before becoming 'Chosen', Jaymie ? Just curious what the threshold tends to be for non-trivial FRs.

useful design's picture
Alastair commented on Philip's Feature Request, “Allow more data types in Calculate node

I like this FR a lot! Math Expression was my favourite patch in QC and the Kineme multiple Expression patch was even cooler.

I think one expression per dimension makes more sense, less confusion in the expressions (but yes more canvas real-estate).

And if we wrote expressions as expressions, we could also have multiple outputs.


Area = PI * Radius ²

Circumference = 2 * PI * r

XPosition = X1 + X2 * timeInterval, where the first data input is a 2D point and the second data input is a real.

I came to this same FR idea thinking about situations where you might have different input and output datatypes… or multiple input datatypes.

E.g. 2x 2D Points in and 1 2D Point Out 2D Point and Real in and 3D Point Out 4x4D Point in and 1x Real Out (Calculation of matrix determinant)

Not sure how best to denote the components from, say, multiple 4D Point inputs… matrix notation is b₂₄ becomes B24, where the 2 is the second input datatype (in this case must be a 4D Point) and 4 is W value of that input datatype.

This might be hard for the math parser if it's using a standard C library. Guess the expressions need pre-parsing already for the I (Calculate List node) and A variables.

Or it could use X = X1 + Y1 * X2 * A, where X is value X in the output, X1 is the X value from the first input (say a 2D Point), Y1 is the Y from the first input point and X2 is the X from the second input datatype (say a real number) and A is a real value input.

For Calculate List nodes sometimes it would be very useful to get to a value in the following index i.e. i + 1 to test the distance to that object or something like that.

In cases where the index was indicated as [i] rather than I and calculation within the square brackets could be done to work out the index number (wrapping indexes the overflow would be very handy to access the first element from a calculation of the last element).

E.g. [i+1], [i-1]

useful design's picture

Awesome Jaymie. So have you already implemented global, local and group sub-comps/nodes (.i.e all three use cases for a container node listed in Option to edit sub-composition without affecting other instance)?

I guess if there is live editing for local sub-compositions it will serve half the purpose of group nodes (known as Marcos in QC), certainly will speed things up a LOT.

So excited to see so much promised for Vuo 1.3.