Did you ever had the problem of debugging a big script that lags, while you're not sure if a block belongs in there? why not making a 'block-disablers' you can attach to blocks like comments, to help debugging?
Supporters:
roijac
owetre18
legoscratch
jji7skyline
cpumaster930
scimonster
veggieman001
Last edited by roijac (2011-09-20 12:51:00)
Offline
Offline
I support. Alice (alice.org) has this, and it'd be nice for Scratch.
Offline
Sounds good. In text-based languages, you would do this with multi-line comment identifiers. In Java this would be */ /*.
I support!
Offline
I support!
Offline
This actually does nothing. And you can identify it easily. And you can just drag it in anywhere and it does its job. And you can unsnap it easily.
Offline
Greatdane wrote:
http://i.imgur.com/AQMpS.gif
This actually does nothing. And you can identify it easily. And you can just drag it in anywhere and it does its job. And you can unsnap it easily.
You can unsnap it easily?! Try it when you have a 50 blocks long script inside three different C's, while your computer *only* has 2GB RAM memory...
Offline
roijac wrote:
Greatdane wrote:
http://i.imgur.com/AQMpS.gif
This actually does nothing. And you can identify it easily. And you can just drag it in anywhere and it does its job. And you can unsnap it easily.You can unsnap it easily?! Try it when you have a 50 blocks long script inside three different C's, while your computer *only* has 2GB RAM memory...
I agree. C blocks are very taxing to RAM and CPU... Even GPU...
It used to take around a minute for the blocks to update on my chatbot when I dragged in or out C blocks simply because the script was so long
Offline
I know: split your script into different sections, using broadcast and wait to connect them, and simply take off the hat of the sections you want to disable. Example:
<when green flag clicked>
<forever>
<broadcast[ something ]and wait c>
<broadcast[ something else ]and wait c>
<if> somthing happens
<broadcast[ a third thing ]and wait c>
Offline
joefarebrother wrote:
I know: split your script into different sections, using broadcast and wait to connect them, and simply take off the hat of the sections you want to disable. Example:
<when green flag clicked>
<forever>
<broadcast[ something ]and wait c>
<broadcast[ something else ]and wait c>
<if> somthing happens
<broadcast[ a third thing ]and wait c>
broadcasting is pretty slow
and editing 30 broadcast names is not fun/fast...
Offline