Hi Barry,
replace /nodes/arrays.js with attached file.
In fact I don't like nodes with large amount of inputs. Later I'll write a new version of this node. I need to find an optimal way to solve this problem.
Great Job! as usual. As a suggestion may be creating other nodes ( Domain nodes ) will eliminate cluttering the nodes with too many inputs (see attached example from Grasshopper).
looks really great! The@'y'@ becomes more and more an powerful and easy to use tool. At the moment, I try to implement the pushFrame-function. Reverse/evaluate the Euler-Angles drives me crazy. RX, RY are working good (after a lot of failures) - and so, every time I think - I got it also with RZ - the axes flips or the angle turns the direction:-( I will post the code next time - maybe someone will have a good idea.
Hi Max,
Thanks for modifying the array.
I understand what you mean about keeping the inputs to a minimum.
I was thinking the same as James ( being able to add a variable into those fields )
That way inputs would only be added when required.
Anyway again many thanks.
Barry
Does the dictionnary multi-languages is running like the old one ?
(because seems not running now ! )
I have changed the "EN" to "FR" and add the French dictionnary with good syntax, run Moi In French but...all stay in English!
Not yet tranlated anything except the core/lang.js --- does this explain that ?
Seems Nodes must be translated !
Motor's animation runs fine!
PS A number of version, and name of the file node used will be fine somewhere in the Node Editor Screen!
I like the idea of optional inputs.
I find the idea of using variables for them okay, but not 100% straight forward.
Grasshopper has it on some nodes that if you zoom in deeper, you can activate additional inputs.
Usine, a node based audio application has three interface states for nodes: "Collapsed" (no inputs visible, all wires go to one visual port, node is as small as possible), "Used Inputs" (only the most important inputs and those actually in use are visible) and "All" (all available inputs are visible). So you can noodle away with all inputs visible and then collapse to one of the two other states later.
I could also imagine that you could "activate" a field as input in the inspector GUI.
Sharif
Good idea, I'll think about it later. Not now.
James
>>A possibly simpler alternative would be to allow range fields to accept variables as shown.
I thought about it. At first I need to check a performance of this node. If implementation of this feature will not lower an overall performance, I'll add it.
Karsten
>> At the moment, I try to implement the pushFrame-function
Yes, it's not as easy as it looks. :) I also wrote RX RY reverse transformation in the SphereArray node. Need to think about RZ.
Pilou
>>I have changed the "EN" to "FR" and add the French dictionnary with good syntax, run Moi In French but...all stay in English!
change lang.set("EN") line in index.html file
Tom
>>a node based audio application has three interface states for nodes: "Collapsed" ... "Used Inputs" .. and "All"
I like this! It will not so easy to implement, but I'll try it.
@Max here the
File lang.js with "EN", but put "FR" change nothing even input "FR" inside the Index.html !
lang.set("FR"); https://we.tl/dNcE2OGmpu valuable till 10 / May / 2016
A big mystery!
Shortcut is this one ?
moi.ui.createDialog( 'nodeeditor/index.html', 'resizeable,defaultWidth:680,defaultHeight:420', moi.ui.mainWindow )
Can you give me the list of the \ui\nodeeditor\...
Domains.png
