@oid said:
I used [value] because add works off the last value that was output and [value] keeps things neater than tying lots of stuff to a single [float].
Yes its convenient, I have tried to add a global function to share the variable "var" between several instances. [v] is good for this purpose. Use case: for example one instance with a list with "add" +1, and another instance with a list with "add" -1. And they are triggered independently.
It would be good to be able to have different groups (like "exclusive" groups).
I also see a use case for several "var" (var0, var1, var2, var3 etc)
...adding a global mode, exclusive groups, idle-reset, and so forth are configuration settings, not part of the live output. Question is where this should go. In the text file also? Or in another text file? Or if they are just a few, maybe just as arguments in the abstraction. The config settings should be retained. It would also be good if one could write the text to use as an argument in the abstraction: [tracky mycommands]. Not sure how to do that.
Slightly annoying and could be fixed but would be less efficient, so I just remember that when patching commands which push a list, the list needs to be backwards or it will cause confusion elsewhere.
that is fine, I just need to include some instructions on how the syntax goes.
We will deal with that in the next post and start really exploiting that this is a programming language and will save you work as any programming language should.
The problem that arise is that when I start to improvise I kind of "break the (your) concept". And I would like to avoid ending up in another patch that is so messy that I can not use it if I bring it up after a half a year or so. Lets continue working on it!
Edit2: No, that loop will not quite work, for got to resend the float to $0-goto on each iteration, only loops once.
I have given your loop code several shots but I can not figure out how to get it working. I managed to (in a messy way) to have it repeat for x times, or loop forever, or loop just once. But never loop x times and then be ready again to to loop x times.
Current patch: