>> Could you provide more information on the error you are getting with the negative values? <<
I'm not getting an error message, however the spiral disappears for any "Turns" value less than 0.01 or negative. This is logical for the MoI3d UI but less so for NE particularly with multiprocessing applications.
Have a look at the attached .nod file. It might better explain my meaning from earlier suggestion of improvement to spiral node. Firstly, dial through the GREEN knob from min-max.
In the upper example the spiral disappears when the knob for "Turns" input is dialled below 0.01, whereas the lower example works throughout the range from -5to5 with the addition of a rather clumsy workaround.
It is perhaps not that straightforward, but if you look at the math & compare nodes on the lower example. I was suggesting incorporating analogous code into the Spiral node and removing any reference to "Reverse" from the info panel or the node itself for that matter. Which is to say, that the negative or positive property of the "turns" value, alone, would designate the direction of twist.
an example of bundleArray - here for points. It takes points from the input and bundle it to packages in the output array. Here the first point of each input and so on.
Works also for numbers and objects.
If you enjoyed contributing the "Spiral" node and are scouting out a new task to sink your teeth into, please have a look at the attached files.
They are the scripting for "SubdivClassic" script, which performs CatmullClark or Planar subdivision of planar polysurfaces. If you are not familiar with the script, here is the original thread posting: http://moi3d.com/forum/index.php?webtag=MOI&msg=6674.164
(Note that the attached files are more uptodate than those in the thread post)
This functionality would be a supremely useful addition to NE toolbox because the faceting of surfaces provides the underpinnings of a panelling system. That is to say, that each subdivided facet (particularly if constrained to quads) services as a target surface for populating with a unit panel with use of "Flow" node.
No doubt the transposing of a standard UI element such as Spiral tool into a node, is more straightforward, but let me know if this is something you could do.
I would be greatly appreciative of anything that extends the functionality of NE. I feel that my efforts to promote MoI as a viable parametric solution on instagram may be undermined by my starting to repeat myself.
Hi Marco, yes unfortunately there are only 24 hours in a day. I have to be careful in what I try to accomplish with MoI so that I can make it be a high quality tool. In general things that have a high amount of support time required are less practical for me to focus on.
Marco reminded me of another node that would have great utility: the LassoSel Node.
He has already done much of the coding required in his "Lasso Select and SelectCurveByContainer".
It can be found in this thread including PDF instructions for installation & operation: http://moi3d.com/forum/index.php?webtag=MOI&msg=8830.1
In essence, any planar shape (circle, polygon or closed curve) would serve as a selection mask.
It would ideally have 2 options:"overlap" (select all objects wholly within the mask only) and "overlay" (select all objects wholly & partially within the mask, like in image below).
"Hi Marco, yes unfortunately there are only 24 hours in a day..."
I understand and respect your choice because I know very well the hard life of a software developer and of a "one man" company :)
And unfortunately this is a big limitation in some situation.
It's a situation that have its strength and weakness.
I know very well...it's part of my life too.
I only wanted to say that it's really a pity that a MAGNIFICENT and AMAZING duo like Moi and Max's scripts (above all Node Editor) can't live a shared "story".
I always thought that bringing Node Editor and all Max's SUPERB scripts into the CORE of Moi it could have been a GAME CHANGER for Moi.
Something that could have been RAISED your excellent Moi to a greater, very unique, level.
I know that probably this situation never will and this is unfortunate for all Moi's community.
But , unfortunately or...fortunately, it depends on point of view :) as I've said some times here during the last two years, for the moment, the funny days when I had some good time to devote to Moi are gone.
From 2018 I never had really more enough spare free time to write something serious for Moi's scripting environment.
I'm always engaged in other different things regarding my "developer life" :)
But you reminds me the funny days when I had TONS of ideas for writing some cool and unique stuff, like for example the "LASSO" script (for what I know I was the very first to do a real (almost) working implementation of that), the "COMMAND FINDER", the "HOLES FINDER", and other useful stuff that I wanted to bring into Moi.
All the code I've written, although working, was nothing more than a "provocation" for someone more skilled than me in Javascript and Math related things, to bring some new cool stuff into Moi.
I had many other ideas into my mind that only waited to be translated into actual working code, but I never had time to do that and also never had the "math science" into my veins :)
Anyway...also I MISSED almost all the code I've written :)
I've found here and there only some stuff, for example the original post I've written related to the "final" version of the LASSO tool.
> I only wanted to say that it's really a pity that a MAGNIFICENT and AMAZING duo like Moi
> and Max's scripts (above all Node Editor) can't live a shared "story".
>
> I always thought that bringing Node Editor and all Max's SUPERB scripts into the CORE of Moi
> it could have been a GAME CHANGER for Moi.
>
> Something that could have been RAISED your excellent Moi to a greater, very unique, level.
Focusing my very limited time heavily on the node editor would be cool but it would probably be a product ending strategic error.
The reality is that the end result of what you're describing would not be very unique since Rhino/Grasshopper already exists in that role and has far more momentum and resources behind it than what I would be able to muster.
That's not meant to take anything away from Max's work, it's amazing what he has been able to accomplish and it's really cool that it's available. It's just not really feasible for me to focus on it myself.
Thank you for the project request. I am still feeling my way around the NE code. More practice is required before taking on more challenging nodes like the subdiv script. Currently working on a new node, but it is too early to publish any beta's. Hint: I am having difficulty placing an image on a node canvas. Yes, I have read all the API's and the basic Javascripts on how to do it. But Elephant is a different animal... :-).
SpiralWorkAround.nod