Variadic if-else reporter

[sathvikrias]

Considering the if <> { } @addInput block has been variadic for a while, I found it strange that the if <> then [] else[] block has stayed the same. I have way too many projects with much too many nested if <> then [] else[] s, which could have been much more elegant (and possibly faster) if we had this as a primitive.
Now, of course you can make this in snap, but of course it's slower, and the line spacing is fully messed up.

now, to make it look good, I think every if else case should be on a new line.
finally, here is the primitive definition

[bh]

Yeah, that's a reasonable idea.

[sathvikrias]

nice, that's good to hear.

[blockpointstudios]

On a similar topic, will if <> { } else { } be deprecated? It's now redundant.

[bh]

@blockpointstudios

On a similar topic, will ifelse be deprecated? It's now redundant.

I actually find myself using it more than ever. Where I used to say

I now prefer IF/ELSE because I find

uglier.

[sathvikrias]

in your opinion, would if <> then [] @addInput else [] :: control reporter also be ugly?

[blockpointstudios]

Well, wouldn't it be if <> then [] else if <> []@delInput@addInput:: control reporter?

[sathvikrias]

import the script pic (in the OP) and you'll see what I mean.
(there must be a default value because a reporter must report in snap)

[blockpointstudios]

But why is there an else case?

[sathvikrias]

well, if every condition is false, then the reporter wouldn't report!

[blockpointstudios]

No, what I mean is: why is there an else case if the variadic if-else command doesn't have one?

[bh]

@blockpointstudios

No, what I mean is: why is there an else case if the variadic if-else command doesn't have one?

They answered that: It's okay for a command block (such as IF) to do nothing, but it's not okay for a reporter (again, such as IF) not to report a value. Thus, the ELSE case is optional for the command, but required for the reporter.

[blockpointstudios]

Oops. Thank you.

[qw23]

Demo

[sathvikrias]

I'm really confused; I already made a working one in the original post, does this to something differently?

[qw23]

It’s simplified: less input items. Plus it has a line break before every condition or potential result. I would’ve preferred a line break before every condition only, but I don’t think that’s possible with current Snap!

[mark4sisb]

@qw23

It’s simplified: less input items. Plus it has a line break before every condition or potential result. I would’ve preferred a line break before every condition only, but I don’t think that’s possible with current Snap*!*

Becomes

You just have to use "Expand" instead of "Separator".