- try making a block with group input c slots
- place the blocks in there
- then reload
you’re trying to make a nested variadic slot. Don’t.
Didn’t you remove that ability (aside from obscure methods like XML editing) at one point? Or am I misremembering? I guess it isn’t that important given this can only be caused by metaprogramming or group input slots, which won’t be being used by someone who doesn’t know what they’re doing.
input slot groups with c-shaped blocks totally work
I didn’t yet take out every (stupid) idea that people might try on metaprogramming and whatnot. But this encourages me again to be much more restrictive 
I meant the ability to add variadic inputs to variadic inputs. I just thought that the ability to make such things had been removed from the dialogue and perhaps even metaprogramming:
However, looking at the previous versions, it seems I’ve misremembered.
I don’t know Snap’s source or JavaScript - so take what I say here with a grain of salt. I would be slightly concerned that runtime checks by metaprogramming blocks for invalid slot combinations (aka variadics in variadics) could slow things down but, on the other hand, I don’t think I ever use (or anyone needs to ever use) metaprogramming in a resource intensive situation. I digress.
yes, I did add checks for certain combinations that aren’t supported, but not yet for all of them. Mostly, because a) this is still under construction, but mainly b) this is for us devs so we can develop time-critical extensions more quickly ourselves. It’s much more efficient for us to develop and debug these domain-specific languages around certain high level custom data structures in Snap itself than to keep piling up yet more JavaScript slop. We’ve committed to shipping rather large, complex Snap!-based applications in a very short time, and they need to be end-user ready within weeks. This is what we’re doing right now, at this time and at this stage of development I don’t care much / at all about anybody getting lost or hitting a rough spot in metaprogramming. So please don’t report any “bugs” or issues that involve metaprogramming etc. I know, I know, y’all love nothing more than those “secret” numbes etc., and I love it when you find them useful yourselves, but this is not the curriculum we’re developing, this is not for learners, not even for end users. Thanks!
I’ve been very impressed at the rapid influx of new features and libraries (!) every time I look at dev. You’re doing great work, and on behalf of the Snap community I would like to thank you.
Yeah, I agree. Let them come to the forum for help if they can’t figure it out, and we’ll help. With the great power of metaprogramming you can do kind of screwy stuff sometimes, and that is something we have to accept.
hehe, no thanks
I thought they were referring to the glitch that happens when loading a grouped input from XML/SCript Pics when there are expands.
see my example above, no bug.
Unrelated to the issue itself, but instead of using an extension, use ([lower case V] of text []). And instead of messing with Unicode values (my pet peeve), just use ([upper case V] of text []). Regarding the latter, it was because of that that you can see that the hello world did not have a space.