Message format is varying depending on send payload

Bug reports Snap! Bugs
1

I'm playing around using send and I'm noticing this

If use 1st block
image

But if I use 2nd block and send a list
image

2

We're thinking about removing the message reporter, because it's prone to cause race conditions. You might as well share data over a shared (global) variable instead of hijacking the message one and then parsing what's in there.

3

OK. I won't rely on the message object from now on.

4

The message format looks the same to me, it's just displayed differently in the two images.

Result of sending "Test"
image
Result of sending a list in table view
image
Result of sending a list in list view
image

5

of course :slight_smile: silly me :slight_smile:

6

It's because
[scratchblocks]
send [test v] to [Sprite v] :: control
[/scratchblocks]

is the same as

[scratchblocks]broadcast (list [test] (list [Sprite] @delInput @addInput :: list) @delInput @addInput :: list) :: control[/scratchblocks]

and

[scratchblocks]send (list [a] [b] [c] [d] @delInput @addInput :: list) to [Sprite v] :: control[/scratchblocks]

is the same as

[scratchblocks]broadcast (list (list [a] [b] [c] [d] @delInput @addInput :: list) (list [Sprite] @delInput @addInput :: list) @delInput @addInput :: list) :: control[/scratchblocks]

(i think)