
when you click the menu, it turns 15 degrees, i find it cool
Here’s a different thing (exuse me for the Split!, you can still drag this into
):
![]()
lol that is so funny
for those who don’t know, Split! is Snap! but Scratch. just search for it on the forums website to see it
Is it the Split! that’s funny; or the actual block I made?
We all know what Split is, right?
how do u know some random user who stumbles by this post is gonna know about Split!?
it’s funny that you’re using Split! to showcase it in my opinion
still, not every person on forums read that
i guess youre kinda right
i do know it but i prefer snap as is
that’s fine, i think we (me, @d016, and many others) made it for beginners and people who like a more “simple” style
I used split to showcase the block mostly because I was too lazy to import the block into snap:
search bar
this one doesnt work
![]()
which i guess makes sense because why should clicking a menu make it report something
i also made this project manager, its simple though:
![]()
Heres a fun one:
![]()
Change the first menu, and the final item will update.
Since you can store block variables and access them across block hats, this is basically a mini Snap! instance just.. without the stage, sprites, and just input slots and and a dream. But eh, you can still access (albeit that kinda ruins the one-block system) the stage, and you could create a sprite and tell it to do stuff.
Once again:
![]()
Click the dropdown, and the counter should increase by 1 every second.
I did figure out something, and it is that you can NOT get the latest value of something by its variable in a forever loop or such, it always sticks with what it was. So you can’t change settings while its running (well, maybe theres something you can do without slots for settings, e.g. a button to set a block variable).
This is a fun challenge.
I was going to make a console, but then I realized BOTH the multiline and code slot types are unsettable! A lot of other slot types are unsettable (hope this is fixed in the next update). Wait.. you can use multiple inputs! So I can have multiple lines!
i made this

No, it’s because you didn’t make it a list.
Try this:
![]()
how did you do so far - saying you did end up doing that
You mean the console? I kinda gave up on it if so
one thing that would help with programming this is a signals block signal slot [a V] as [menu V] :: control which would call the respective when slot [a V] signals [menu V] in the block, another thing that would help is if you could signal this from outside of the block, like this
tell ({my block [special input V]} :: ring) to ({signal slot [special input V] as [menu V] :: control} :: ring) @:>
or
tell ({my block [special input V]} :: ring) to ({set slot [special input V] to [Something else]} :: ring) @:>

