Text to Layer/Image (automatically generated text layer)
This one seems limited to me, since it would always output a text layer with the same center, font, and color. How do you envision using it?
Fair enough. I think it would be most useful while a composition is still in development. It would give one more option for keeping track of a value without needing a console window, or even the Vuo Editor in view. I see it as a way to just get some text onto the screen without any fuss; just plug text into a layer input, and off you go.
I guess what I had in mind was that text could be converted to something like a 2D Point. The summarized version of a 2D Point looks like: 1.2, 3.4. Couldn't this be used instead of having to make another node to convert it to JSON?
There is a node "Fire event periodically". I wonder what is a proper way of receiving this kind of values as a subcomposition's published input. Does it make any difference if the event is received as an Interger input or Boolean input or any other?
Can the Calculate node be changed to allow for integer arithmetic? I know the automatic type converters kick in when it's hooked up to nodes that take Integers, but being able to set the type of the Calculate to Integer node would cause less clutter, less time selecting how to round the result, and less processing time in a loop.
Additionally, can it be changed to also allow 2/3/4D Points? In the event that a 3D Point is being used in a calculation, and the result is another 3D Point, right now three Calculate nodes need to be used, one per dimension. A point could be constructed within an expression using [these] brackets. A number could be used in an expression without any change, but perhaps a 2D Point could be written with _XY as a suffix, a 3D Point with _XYZ, etc. A dimension could be used from a point with just that dimension (instead of all dimensions) specified in the suffix.
The node could either take a single expression to calculate all dimensions in the point, or it could take an expression per dimension. Allowing for a bit of vector-style arithmetic could further open up some flexibility too, for example, by allowing adding two points, multiplying a point by a constant, multiplying dimensions (as in X1*X2, Y1*Y2, etc.), dot/cross products, a magnitude function (perhaps with |this| syntax...
Expressions might look like this:
radius * [cos(theta), sin(theta)] //Point on a circle at angle theta
deltaTime * velocity_XY + location_XY //New location after applying velocity
[velocity_X, deltaTime * gravity + velocity_Y] //New velocity after applying gravity