New inline block input just dropped?

image
image
Created by making an multi-input with 15 in the group

@\ego-lay_atman-bay in snapblocks when

what a nice reporter

ALSO JENS, I accidentally found this while searching for the upvar input group to supplement my reply here, I was not up to some crazy, "hackery" stuff

jens is going to hate this... beware.

After messing with more group IDs, I figured out that these are special inputs used in only one or two blocks each. I don't know where this is used, but sorry if this doesn't constitute as a valid bug

Jens, unfortunately, disapproves of a lot. Nethertheless, this is still a bug.

yeah, makes sense.

you can always use untitled script pic(32) (slot 15 is the c-shape w/ arrow).

is this an official block?
Edit: nope, but this is genius ngl

They're just c-shapes with the loop arrow, you can make them in custom blocks with the gui (no metaprogramming or input group necessary).

When (or if) I figure out a way to make input groups (so that a group of inputs can be placed vertically on one line).

I see this now. But this is still a visual (and functional) bug.


image

works fine, but


glitches

So it's basically an inline loop C-slot that does absolutely nothing? Probably very useful :slight_smile:

reminds me of this

christ

here before jens absolutely kills this topic


edit: this monstrosity as well

interesting, why does launch make it work?
also, why must you assume the worst of Jens?

An error occurred: Body seems unclear, is it a complete sentence?

Is this a complete sentence?

It is not due to the lack of a "the" at the beginning of the sentence, which is why it's conjoined to another sentence with a comma.

Well....Those two independent clauses should be separated by a semicolon or period, but anyway...

tHeRe NeEdS tO bE a "the"

But can we please return to the weird inline block input and not sentence structure?! lol


(15, 14, 16)

uhh... I think this may be removed soon

10.3.5:

Notable Fixes:
    disabled some theoretical albeit unsupported programmatical variadic slot settings

2024-12-23

threads: added some guards against *redacted in case you don't want to see the word*
prepared v10.3.5 patch

@jens only disabled it with variadic inputs (just slots like 115), but not groups (even though the first post explains how to do it using input groups instead of with metaprogramming). It also disabled all the built in variadic groups from being variadic (script vars, send data, receivers, and else if), though he didn't actually disable creating them through the gui (if you make a variadic input, send data, recievers, and conditionals (else if) are selectable under the cog > special).

That's not my sentence...?