Weird broken unringed return value that cant be dragged

Help with Snap! Snap! Editor
1

broken
(item (3 v) of (split (join (ring (join)) (ring (join)) (ring (move (10) steps))) by [blocks v]))
upload://lRunv4GUntVIha7wGOTzK1Zx7LC.png
normal
(ring (move (10) steps))
upload://rN8GURbhMe1SN6ziEdDTMTrSW5i.png

2

link to project

3

use [sb]...[/sb]
This thing is not that broken, it is actually quite useful. I am Very glad the developers kept it in. Try putting it in a say [ block. Then, you can click it from the say window itself.

4

i think it might be a bug though, because it is returning a block without a ring, but very cool i can press it in the say window, AND DRAG FROM IT, its as if tthe say window WAS a thing

5

Seems normal to me...
I don't know how to explain it, but the output makes sense.
I'm pretty sure it's supposed to do that.
I don't see a use for it either way, but yeah, I think it's fine.

6

then you can take out the block from the say bubble and cursed blank bubble

7

Okay, maybe it's a bug, but it's actually pretty cool.
The weird thing might be that it's telling itself to render a block, not report one. Then it somehow turns the bubble into a code space to render the block in.
Might be wrong, but it's just a thought.

8

yes, actually this is one major advantage that snap has over many programming languages.

I have also a few posts about this, and I have a "ringless" custom block too. There are many ways to do it, as you can see.

I think basically the CommandBlockMorph is being told to render in the say bubble instead of a RingMorph, and a CommandBlockMorph is always able to be used as something that you can run or build on to make a bigger script. I'm probably wrong though.

9

Oh, haha, I thought you were talking about Snap!Blocks.

10

oh, thats fine.

11

imagine the possibilities, you could make coding games easier, because just make things on the stage with llike saying blocks, and you could drag them

12

actually i think your right

13

about what?

14

the thing you said you might be wrong

15

Yeah, that's essentially what I was thinking.

16 
{+ move + ((a)) + steps + :: motion} :: hat define
move (a) steps
i figured out snapblocks
17

I think there's a way for define hats to insert the plus signs automatically, I just forget how...

18

{ ::ring}
broken ring

19

hey you know (ri{}ngs) why isnt the middle blank

20

If you want to mess around with Snap!Blocks, I think you should go do that in the post for it instead. (I don't know if it's considered spam or not either way, so I would test it some other time.)
Otherwise, all the messages will just be clutter. :slight_smile: