Follows on from another post last month but now I've had more time to play and structure my thoughts
When using a python handler to listen out for Scratch 1.4 broadcasts and control Raspberry Pi pins and addon boards, I use two techniques:-
Basic method is to just enter a new message in the broadcast block but that means typing a complete new message for every pin off/on command, as shown in top row
A better way (if there were lots of different commands to be sent) is to use join blocks as shown in the 2nd row
Using Snap!, I can create custom join reporters with pull-down menus and make life easier and reduce syntax errors as shown below. Very nice
But, I'm in a quandary as to how to present an equivalent reporter when it only returns a single string
Here are the options I've come up with
The 1st row shows the old Scratch way - just plain type in the value
2nd row shows a reporter with no label. No block (that I've seen) has no label so this is very un-Snap! like
3rd row uses word. No primitive block uses that and there isn't one like it in a library (there is words but no word) but I feel it does visually signal, quite well, that it will return the word UnicornHAT.
4th row uses join. Join is well known for returning a string but I feel that since I'm not "joining" anything together, that it looks a bit silly.
5th row uses report. There is no existing report reporter block but there is the report command block so I think that this also visually signals quite well what it does.
So what do people think?
Which one should I use?
Or is there an existing library block that I should copy its look and then modify the copy to add my pull-down menu?