After much study learning how the Motor2.nod works, I did a documentation PDF.
Also, there were 3 miscellaneous observations of very minor concern:
1. The first rotate node has input label "In" instead of "Objects." (This is apparently an old version leftover?)
2. Regarding arcsin (asin), the order of mathematical operation appears to be
nonstandard. (An additional set of () was added around the asin opperands.)
3. The Rotate nodes Z angle inputs are obeying the "Left Hand Rule," rather than the "Right Hand Rule." (OK I guess)
4. Increasing positive angle results in Clockwise rotation. (OK)
- Brian
The Word to PDF conversion makes the SnagIt MoI PNG blurry :-(
So I need a different way to make the PNG?
Edit: Updated PDF with new Figure 1 PNG from CustomUI Snapshot Right Click, and added a couple of sentences.
<<So I need a different way to make the PNG?
You have no choice to make different level of rendering image at the begining of the PDF process?
Seems remember that ...but a long time that i don't made a PDF! (i have not more this program)
Blurry for me only when you make a big zom!
French translation of your Tutorial in a few days! :)
Quartz is in the translate list.
Quartz is also a basic node, but its activation is commented out in the basic.js file.
Quartz refers to a quartz watch.
To activate Quartz, by editing the basic.js file, uncomment it by changing //LiteGraph.registerNodeType("Basic/Quartz", Quartz);
to: LiteGraph.registerNodeType("Basic/Quartz", Quartz);
Try replacing the slider in motor2.nod with a Quartz node for slow, continuous animation.
The Hz (Hertz) input should control cycles per second, somehow?
The Hz input does not seem to do anything?
- Brian
Hmm, there is also a Watch node...
The Watch node can be wired in just after the Quartz node.
The Watch node displays the input numbers. With Quartz, the numbers go from 0 to 359.
Quartz can have its step value changed, and has a tic-tac mode.
Have you got some good news about a new official release of your NodeEditor ?
In my garbage time i'm continuing to code some new utility nodes for PointArray or in general but,
if i remember correctly, you said that the next version of NodeEditor will present a major rewrite of the fundamental datatypes,
so i would like to know if it's better for me to wait the new version, instead of coding nodes that will not work anymore.
Hi Marco!
I'm fine, thank you! :)
I have no time for programming right now, but it will not last for long. Wait two or three weeks.
>> the next version of NodeEditor will present a major rewrite of the fundamental datatypes
I have plans to replace Number type with NumberArray type. It should be last change in the datatype system.
> I have plans to replace Number type with NumberArray type. It should be last change in the datatype system.
Thank you for this heads-up.
I think that it shouldn't be a problem for the utility nodes i'm coding, for the PointArray datatype.
One more question, just about the PointArray.
Did you plan to code some business logic that will supply programmatic ways to select the PointArray's element ?
I realize that i've already asked this in other posts and with other words,
but i think that this would be a very very powerful thing.
For the time being, i've only written the "PatternSelArray" node, but it can be done much, much more :)
I made a lot of changes in the internal structure today. The work goes faster than expected. :)
Right now I rewrite all nodes for using numarrays as input data. It will take couple of days.
Wait for the new version next week.
Motor2Doc03.pdf