Today I was testing out a game I'm working on, and found that the most probable cause of the error was a couple of blocks in the middle of a long script...I had to remove all the blocks below the possible errors, the remove the errors, then put the lower half back--only to find that those blocks weren't the cause of the problem at all! It got annoying to have to repeat that process until I finally found the error after several tries.
This feature would allow you to right-click a block and click 'disable' from a drop-down menu. The block would appear grayed-out, but still present: it would appear in the code but wouldn't affect the script at all. If you wanted to enable a block again and restore its functionality, just right-click and select 'enable', and voila--the block works again.
This feature would be quite useful when developing experimental features in projects, such as additional visual effects, items in games, game modes, etc.--all without removing any blocks.
Additionally, there could be a feature that saves a copy of the project without all the disabled scripts--this could save space in the finished project for uploading, while keeping the disabled scripts in the original project in case you want to expand your project with the disabled experimental features.
I think this would greatly help new Scratchers determine problems in their scripts, and think the Scratch Team should consider adding this in Scratch 2.0.
Discuss?
Offline
This is a great idea! Like putting code in comments in most languages.
Offline
this is my suggestion!
created few days ago... should I add you both as supporters?
Offline
roijac wrote:
this is my suggestion!
![]()
created few days ago... should I add you both as supporters?
I didn't see that xD
But sure, I definitely support
Offline