Hello James,

in short, because I have an appointment now. Try right click on the node to switch to objects and think about switching the compare node to a|b. I'm not sure what the result should be. Maybe more in the evening (CET).

Have a nice day
Karsten

UPDATED

Thanks Karsten,

How profoundly stupid of me not to have checked to see if the node had alternate modes.

I was trying to make an H-Tree Pattern, only as a first step in exploring recursive patterns.
just as Wayne has done here: http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.1702

However, this would only be a starting point; I would like to explore a broader scope of recursive patterns.

Thanks again
James
https://www.instagram.com/nodeology/

So there is only one "loop", but the loop can be used for multiple cycles. (?)
Nesting of loops?

- Brian 3+ years

Hi, James.
Example of using the "Loop Start" and "Loop End" nodes.

Hi WN,

Welcome to the forum.

Wayne
https://www.instagram.com/waynejhill/

Hi Wayne.

Thanks!

Wayne,

Yes exactly, but as I said "only as a first step in exploring recursive patterns"
I have updated my earlier post with link to your posted image.

Brian,
Yes exactly! "Nesting of loops".

WN,
Welcome & thanks for the attachments.
They are not what I'm looking for, but I hope these are the first of many posts
of your node experiments - playing with nodes.

Thanks to all of you,
Have a great weekend,
James
https://www.instagram.com/nodeology/

Hello Karsten,

This may not help with my particular requirements, but as a first step in that direction,
if "LoopEnd" node was inline with the "Output" node rather than branched off prior
with "clone" node, then each iteration could be recorded and if the option selected, outputted.

Does that make sense?

James
https://www.instagram.com/nodeology/

Hello James,
yep! Maybe a solution for the problem not to loop all data again. The loop stuff is only a q'n'd' draft and it took a year that someone was asking for. So I've never thought about it in the past again. I had to look twice to understand what I have done here;-)
Maybe we need a second array to store and push collected data? I'm not sure how we can realize it.
Any idea is wellcome!

A nice day to all
Karsten

NE -> Gordians_Knot_Puzzle.

Hello James,

I'm trying to find a solution at the moment for the loop stuff - difficult, because no time and written no code since one year. By the way - Could someone explain me nested loops??? Loops in loops?


Not finished, but a first step for an experiment. Only one loop at the moment (think about a solution), but a cumulated output.

Only for experiments!

A nice day to all
Karsten

p.s.: @WN -it seems you have fun!

Karsten,

Thank you for getting back to me.

The new loopEnd node looks promising.

It was clever to use splitPt - ptExt to strip out the rotational data from the point instances.

I repurposed your wiring to do a "drunken walk" (a staple introductory exercise in computer graphics).

A video can be found here:
https://www.instagram.com/p/CDi5Uw1J_5s/

nod file attached
Nested Loops

Nested loops are loops within loops...this video gives a clear description:
https://www.youtube.com/watch?v=1c1_TMdf8b8

I'm not sure how this may work with nodes. I'll see if I can build something.

Thanks again,
James
https://www.instagram.com/nodeology/

Hello James,
loop in a loop, not really a surprise - but I didn't know that it is called nested loops:-)
The Problem here:

- I have to use global variables that LoopEnd and LoopStart can exchange informations - at the Moment only one with a fixed Name is present
- I'm not sure what I should use for multiple ones (Maps, sets, or named ones)

- I'm not sure how the NE reacts to multiple timers? Is it neccesary?

Some experiments have to be done the next time.
And thank you for the example - I will try it in the evening!

Thank you
and
have a nice day

Karsten

Fun start fun!

A cool one is this

Karsten,

"not sure how the NE reacts to multiple timers?"
There is no issue with multiple timers



"Is it neccesary?"
In most cases the same timer could be utilised for multiple loops.
There would need to be a triggering of second loop after first has met end condition.

Perhaps logic/compare a=0 (end condition for earlier loop) initiates new loopStart (trigger).

"global variables"
There does need to be a means of having unique variables for each loop.
Ideally, NE would recognise multiple loopStart/loopEnd pairs and attribute unique designators. Alternatively users could manually name each node pair, which would serve as the variable name. This approach though could be fraught with difficulties in terms of UX.

Would it be possible to have direct wire link between pairs, so loopStart get a randomly generated numerical designator on placement on the canvas, & then it is sent to LoopEnd via green wire?

Another alternative would be to introduce a txt string data type wire. It could also be used to externalise text inputting into “text” node. It may well have over uses.

Please let me know
James
https://www.instagram.com/nodeology/

Hello James,
wireing is my favorite to exchange the variable names by UIDs. I don't think that we need an additional text type for that. It would also need a lot of work in the base system. Furthermore I'm thinking about time stamps as an internal critera to trigger/reset loops.
How to store and manage the loop data isn't clear for me at the moment also.
One loop is simple, multiple loops not.

Have a nice day
Karsten