Hat blocks should be callback-based, rather than polling-based about scratch-extension-docs HOT 5 CLOSED

ext.currentTrigger = null;

ext.getsEvent = function(which) {
    if (ext.currentTrigger === which) {
        ext.currentTrigger = null;
        // Do stuff
    }
};
ext.sendsEvent = function(which) {
    ext.currentTrigger = which;
};

ext.descriptor = {
    blocks: [
        ['h', 'when event %s sent', 'getsEvent', 'evt1']
        [' ', 'send event %s', 'sendsEvent', 'evt1']
    ]
};

As for "special" events such as what could be 'greenFlag', I'm not sure how you would send those. Probably like you said, ext.trigger("special")?

Note - not tested, but should work.. :P

from scratch-extension-docs.

@liam4 That's exactly the kind of code I'm hoping to avoid..

from scratch-extension-docs.

@bobbybee I see what you mean, but while they don't implement it, it'll work. :P

from scratch-extension-docs.

that's an interesting idea which we may implement at some point. The current implementation supports having hat blocks that accept arguments and we wanted that flexibility. For example, you can currently put a reporter from one extension into a hat block argument of another extension.

from scratch-extension-docs.

@bobbybee Thanks for the suggestion! We have moved the content in this repo to https://github.com/LLK/scratchx/, would you please re-open this feature request on that repo?

from scratch-extension-docs.