I'm working on a music microworld where notes are blocks , tunes are scripts and few other blocks help composers-begginers to transform tunes .
I'm having some issues with the functionality that deals with blocks' metadata ( and ) when used with blocks that depend on . Here is a sample project with the issue isolated: Snap! Build Your Own Blocks
TuneScope is great and one can do amazing things with it. For some reason the operations over the list of notes are not included in this version...
I like the idea of having a note/tune as a thing (script) that you can click on and listen to it, and then you can put the same object (script) inside another block to manipulate it and hear the result immediatelly. This way you don't have to talk about lists when introducing it. I blieve at some point I'll put the mechanism inside TuneScope. This is a link to the work in progress: Snap! Build Your Own Blocks
DO# is a valid notation. Just like you can play BACH, you can play MI-LA SI MI DO-RE which in Bulgarian means You are dear to me, Dore.
Not sure why the other one doesn't work and what's the differense with this one. As far as I get it, with the of reporter we get the launch block in the context of the Sprite, which apperantly is not really the case in the example that crashes.
This macro capability isn’t fully implemented. First, we shouldn’t have to use the calling script as an explicit input to the macro. In a later release, this will be fixed; when defining a block you’ll be able to say that it’s a macro, and it will automatically get its caller’s context as an invisible input
So the example can be modified
The result of split >> join is not always directly runnable as explained above (and results are slightly inconsistent)