Filtering out these two observations from the EVERY thread:

:+1:

I’m also open to these ideas.

1 Like

doesn’t IF see anything non-zero as true? so there’s no need for EZ in there.

EQ Z MOD X Y

logically is the same as

MOD X Y

right?

edit: checked, yes, non-zero is true for IF

edit again: gah, i was thinking EZ not EQ Z

you mean EQ? it’s not equivalent though. consider the following script:

IF MOD T 3: TR.P 1
IF EQ 2 MOD T 3: TR.P 2
T WRAP + T 1 1 4

triggers will output the following:

T:   12341234
TR1: 11011101
TR2: 01000100

apologies, i read the intention as checking against zero— i totally missed the point.

i get what you’re saying now and it makes sense.

1 Like

Not sure if this thread is dead or if we need a separate thread to discuss potential future operators 2.2, 2.3 and beyond… BUT…

I think a ratchet operator would be extremely useful. I’ve put ratcheting into a few teletype scenes, but in the latest one I was working on, I found the constraints of the DEL pre insurmountable for what I was trying to do.

TR.RATCHET (TR.RAT or TR.R?) with arguments for how many ratchets and delay between ratchets would be a really simple and powerful syntax for triggering ratchets on the trigger outputs.

This is the R feature, which is planned for sometime before 3.0.

what’s the status of FN?

I’ll feel like an idiot if it’s already included in one of the betas available
sorry…could not find a definitive answer myself

1 Like

I too am interested in the status of FN. or +1 for FN