| 2106 | 😀 | Suggestion | Please support behaviour parameter ranges. Instead of making me copy the name and mousing around to pass p3, p4, p5, p6, p7, p8, p9, p10, p11, p12 to the 10 input params of one of my many other subroutines that take 10 sequential params along with maybe a couple others (which I do often to represent a list/queue) and it making the graph a mess because of these long input lists (don't get me started on my 20+ versions) it would be incredible if I could just pass in param C~L in one or two boxes in my call instructions!
Ideally this could be defined on the subroutine definition by marking those params as sequential and maybe getting an extra param for a reference to the range itself in the same format as the caller gave them. This way in my subroutine implementation that takes the range can call another subroutine that uses sequential/range params too or, if I choose to deal with specific elements, still get access to p6 directly.
Come to think of it actually none of this would be needed if I could dynamically get a parameter by its number. If you could add an instruction that was just "Get" and if given a variable/static with the number 1 in its input then it stores P1 in the output, etc. plus you would have to have an accompanying Set so that params can be modified by their index too. | | 2023-09-05 19:11:59 |