If you like the node approach to making geometry you might want to check out the Grasshopper system in Rhino, it's more mature and has more dedicated development resources on it.
However, I do not have Rhino at the moment and I love MOI over other CAD modelling tools. So, I think I will wait (for developers to develop more features on Nodeeditor)
I am attempting to simulate the Explodemove of two Voroni patterns extruded as Pilou's demo below, but with a new node on the NE (node editor, elephant some call).
Hi Wayne, inputs for the ExplodeMove factory go like this:
Index 0 : "Objects" - object list of objects to explode.
Index 1: "Scale factor" - numeric value for scale factor.
Index 2: "Origin" - optional origin point for scaling.
Thank you for the quick reply. The input parameters you provided are as expected. This leads to additional code is required to filter the objects types and keep the closed objects together. Back to coding...
Draft of a 3D log spiral node.
For 2D, set zFactor to zero.
This is just an alpha version with little testing.
I want to add arcLength output...
(Code came from powerConeSpiral script.)
Ok, I had to do some deep searches for an answer to my problem. Found the solution to my objects exploding in a rarely referenced documentation by Max Smirnov.
Was wondering what Lont+ meant.
(I did read that post by Max 5 years ago, but never really grasped it.)
Did a slight upgrade of alpha logSpiral node.
But see that Karsten? already did a curve length node.
So (at least some?) MoI curves have a .length property, so I do not have to re-calculate the arcLength...
As per Barry's suggestion, here is a kludged together Macro, using the Concat node, renamed, to enable the creation of a macro node with several lines of text.
Highlight the completed text macro in the nodeeditor canvas, and EXPORT it to the Macro directory, with desired name.
Saving it saves the DocText macro as a node program, so Loading it with Load erases the current canvas screen.
The DocText macro may be entered into a new screen through the right click Macro menu.
Do NOT get the DocText macro with the Load button.
Saving it saves the DocText macro as a node program, so Loading it with Load erases the current canvas screen.
The Macro menu seems to lack a scrolling bar, so space may be limited???
This whole Macro Save vs Export vs Load, versus macroLoad is confusing. There should be a SaveMacro button, and a LoadMacro button? And Macro scroll?
Also, every node Program would need to have its own text macro saved???
Well it is an experimental kludge...I cannot spend any more time on it.
A few simple tests:
It seems that only one master DocText Macro is needed.
The Macro can be right click MacroSelected to the canvas multiple times, and each canvas copy can have its text modified in different ways, and the canvas .nod program saved in a node program.
But the modifications permute the order of the text lines, which is not good.
- Brian
Edit: Macro Import can import the DocText file from some other directory.
Note, the order of the text lines can be changed by Max' addition a few years ago of the ability to Alt+Drag the input Dots to the Macro. (I had forgotten this.)
explodeDemo.nod
