| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(experimental) slotwise inheritance à la Henry Lieberman for
sprite-local variables.
see
http://web.media.mit.edu/~lieber/Lieberary/OOP/Delegation/Delegation.htm
l
Let a sprite inherit another sprite’s local variables by making it the
“parent” in the sprite-icon’s context menu (the button icon in the
sprite corral underneath the stage). The child not only inherits the
variable slot but also - dynamically - the parent variable’s value.
Changing the parent’s variable value also changes it for every child.
If a child uses SET or CHANGE on an inherited variable it automatically
“shadows” it with its own value, thereby stopping dynamic participation
in the parent slot’s value (in effect dis-inheriting that slot).
Deleting a shadowed variable slot once again reinstates its inheritance
status.
inherited variables are shown as “ghosted” both in the child’s
variables palette and in such stage watchers. “Shadowing” them
un-ghosts both the variable blob template in the palette and the
watcher onstage (if any). Deleting a shadowed variable once again
ghosts the watcher and the palette block template.
Delete a (shadowed) variable either via the “Delete a variable” button
in the IDE or using the new “Delete” block in the variables category
|
| | |
|
| |
|
|
| |
happy New Year, duh :-)
|
| |
|
|
|
| |
Don’t highlight scripts running inside clones (boosts performance),
Thanks, @aranlunzer, for the hint!
|
| | |
|
| | |
|
| |
|
|
| |
thanks, Bernat, for reporting this bug!
|
| | |
|
| | |
|
| |
|
|
|
|
| |
make sure to always evaluate the “report” block’s input, even if used
inside a custom command definition, because hardware extensions (and
other reporters with side-effects) rely on it.
|
| |
|
|
| |
now Snap! really *is* Scheme :-)
|
| |
|
|
| |
reducing the stack size for reporters
|
| |
|
|
| |
(commented out, under construction)
|
| | |
|
| |\
| |
| | |
Improvements to Split block for whitespace and line options
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Split by whitespace now uses the built-in definition of whitespace \s
This catches all characters definted as whitespace, see below:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp
* Split a line by all unicode compliant line breaks. The biggest impact here is
that OSX and Windows files will now split the same way.
The cr option is still around, but ther's no longer a need for it, IMO.
|
| | | |
| | |
| | |
| | |
| | | |
and display an error if a reporter or a “called” ring is missing a
“report” statement
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| | |
“stop this block” when used inside a custom block definition now always
returns out of the lexically enclosing script (the definition), even if
it is used inside other nested, C-shaped custom blocks in the
definition code. Previously it only stopped the nearest encompassing
“for” block, now it always stops the block whose definition it is in.
I don’t expect this fix to break any existing projects.
|
| | | |
|
| |\ \
| | |
| | | |
Add missing localizations and add Portuguese translations
|
| | | | |
|
| | |/ |
|
| | |
| |
| |
| | |
thanks, @brianharvey!
|
| | | |
|
| |\ \
| | |
| | | |
Added callback to Process
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| | |
IGNORE INPUTS
this also enables all existing FINCH blocks and other hardware
extensions again, which used the REPORT (HTTP://) pattern
|
| |/
|
|
|
|
|
|
|
| |
REPORT now reports to the nearest lexical element expecting an input
(which may not be the block holding the REPORT statement, this lets you
REPORT out of nested FOR loops).
STOP THIS BLOCK behaves as it used to.
If you’ve been using REPORT instead of STOP THIS BLOCK, you should
migrate.
|
| |
|
|
|
|
| |
enables reporting and stopping a bock from within a C-shaped slot in a
custom block, but not (yet) out of nested C-shaped custom blocks (but
that’s coming up, too)
|
| |
|
|
|
| |
fully copy local variables for sprite duplicates and (Scratch-like)
clones
|
| |
|
|
|
| |
replace UpvarReferences with references to Variable objects, fixes
upvar scope issues
|
| |
|
|
|
| |
introducing Variable objects, all functionality stays the same at this
time
|
| |
|
|
|
| |
you can now redirect “this” in a JS function by binding it to another
sprite using the OF block
|
| |
|
|
| |
hidden option in the shift-context-menu of reporter scripts
|
| | |
|
| | |
|
| |
|
|
| |
Go figure…
|
| |
|
|
|
| |
(e.g. continuations). Brian was complaining about empty continuations
“sucking” up the watchers and value bubbles.
|
| |
|
|
|
| |
deleting variable watchers by dropping them on the palette resulted in
wrong ones to be created when showing them again
|