Changing a block from a command block to a reporter can cause confusing behavior

Steps to reproduce (mac IDE v1.2.77 firmware v237 pico-xrp):

Edit a text library that defines a command block
Load the library into the IDE
Drag the block into the main program area
Modify the text library to make the block a reporter block
Delete the library in the IDE
Load the modified library into the IDE
Observe that the displayed block in the main program area now looks like a reporter block, but when I run it, the return value is not reported as sayIt text.
John M figured out what was wrong by copying the text of the block to the clipboard and observing it looked like a command block, not a reporter block.

I admit this is an obscure corner case. I ran into it when I was trying to debug problem in the block. I turned the reporter block into a command block so I could insert sayIt statements to see what was wrong, then after running that debug version for awhile, I turned the block back into a reporter block (as it was intended to be).

One easy workaround is to just quit microBlocks and start over.

‌

Comments (3)