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!
"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.
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.
I was puzzling over the German "mit -KGV(n,m) * PI <= t <= KGV(n,m) * PI".
So, in English math the German KGV(n,m) is the Least Common Multiple of m and n.
LCM(n,m) is lcm(n,m) in Javascript. (n and m are integers in this example.)
German ggt(n,m) is the Greatest (Largest) Common Divisor, (Javascript gcd(n,m).
In Max's latest version of nodeeditor, unused node dot circles are NOT colored.
I prefer them all to be colored, pink gold and teal.
Does anyone else have this behavior?
I've re-installed different versions of nodeeditor several times...
In the file "colors.js", from the "core " directory, line 38 has a property, 'io_highlight': false //, replace its value with true, node nodes will become colored.
drunkenWalk.nod
