Scratch
archived forums
#1 2010-05-27 07:14:42
Scratch editor is getting slow
I've got a program with 56 sprites in it. I need to copy the same portion of code within the first script 55 times so that sprite1 can check for collision with each of the other sprites and then act appropriately. So all I need to do is duplicate an if block that contains 5 or 6 lines, add it to the end of the script, and then edit all of the references in that block from sprite(n) to sprite(n+1). Unfortunately, every time I duplicate the if block it takes longer and longer to do this. I've put up with this up through sprite18 now, and I'm dreading having to do the remaining sprites 
Is there a way I can edit the *.sb file in another program?
Thanks in advance ....
Most Recent Projects:
Four Bar Linkage Animator: http://scratch.mit.edu/projects/DB88/1102417 ...... Moon Defender: http://scratch.mit.edu/projects/DB88/1092234 ..... BUGS: http://scratch.mit.edu/projects/DB88/1095318
Offline
#2 2010-05-27 07:19:58
Offline
#3 2010-05-27 07:43:55
Re: Scratch editor is getting slow
Nope, there is no way to edit Scratch files anywhere else - it's sad, really, how slow Scratch is. You could try using hacks of Scratch,like rocket101 mentioned "BYOB," but that will probably damage the file for further use within Scratch. The best you can do without exploiting the boundaries of the Scratch application is the make your blocks in little bits and then attach them together later.
Offline
#4 2010-05-27 10:26:49
Re: Scratch editor is getting slow
coolstuff wrote:
Nope, there is no way to edit Scratch files anywhere else - it's sad, really, how slow Scratch is. You could try using hacks of Scratch,like rocket101 mentioned "BYOB," but that will probably damage the file for further use within Scratch. The best you can do without exploiting the boundaries of the Scratch application is the make your blocks in little bits and then attach them together later.
I've been attaching each duplicated block to the main script and then editing it. But you're saying that it should be faster if I duplicate the block, edit it off to the side, and then attach it later, right?
Most Recent Projects:
Four Bar Linkage Animator: http://scratch.mit.edu/projects/DB88/1102417 ...... Moon Defender: http://scratch.mit.edu/projects/DB88/1092234 ..... BUGS: http://scratch.mit.edu/projects/DB88/1095318
Offline
#5 2010-05-27 13:34:54
- MyRedNeptune
- Community Moderator
- Registered: 2007-05-07
- Posts: 1000+
Re: Scratch editor is getting slow
Shut down every program on your computer that you aren't using at the moment... It might make Scratch run faster.
Also, you can try setting Scratch.exe to high priority (Task Manager/Processes tab/right click on Scratch.exe process and set priority to high). That will make your computer focus more on running Scratch and it sometimes also helps me when Scratch is running slow.
I know what you're thinking! "Neptune! Get rid of those filthy advertisements and give us back the Zarathustra siggy, you horrible person!" Well, don't worry about it, the Zara siggy will be back soon, new and improved! ^^ Meanwhile, just do what the sig tells you to. >.>Offline
#6 2010-05-28 16:15:23
Re: Scratch editor is getting slow
DB88 wrote:
coolstuff wrote:
Nope, there is no way to edit Scratch files anywhere else - it's sad, really, how slow Scratch is. You could try using hacks of Scratch,like rocket101 mentioned "BYOB," but that will probably damage the file for further use within Scratch. The best you can do without exploiting the boundaries of the Scratch application is the make your blocks in little bits and then attach them together later.
I've been attaching each duplicated block to the main script and then editing it. But you're saying that it should be faster if I duplicate the block, edit it off to the side, and then attach it later, right?
Working off to the side and attaching things later helped, but my goodness it was a pain trying to get things attached! If I scrolled down to fast, Scratch locked up. If I didn't save after every attachment I made, Scratch locked up. After a successful save, Scratch always went back to displaying the top of the script, so that forced me to have to sloooowly scroll down again. Sometimes I got warnings that Squeak was almost out of memory. The warning box had options like "Proceed" or "Cancel", but none of those options ever worked ... by the time the warning popped up Scratch was locked up.
Definitely frustrating, and I hope this is something the developers are trying to improve.
Regarding the slowness during editting, is this because every time a change is made, Scratch automatically "recompiles" the script so it is ready for immediate execution? If so, would it be possible to add an option to allow the user to decide when to compile? I'd gladly trade off immediate execution ability for a less frustrating editing experience.
Most Recent Projects:
Four Bar Linkage Animator: http://scratch.mit.edu/projects/DB88/1102417 ...... Moon Defender: http://scratch.mit.edu/projects/DB88/1092234 ..... BUGS: http://scratch.mit.edu/projects/DB88/1095318
Offline
#7 2010-05-28 16:18:33
Re: Scratch editor is getting slow
DB88 wrote:
DB88 wrote:
coolstuff wrote:
Nope, there is no way to edit Scratch files anywhere else - it's sad, really, how slow Scratch is. You could try using hacks of Scratch,like rocket101 mentioned "BYOB," but that will probably damage the file for further use within Scratch. The best you can do without exploiting the boundaries of the Scratch application is the make your blocks in little bits and then attach them together later.
I've been attaching each duplicated block to the main script and then editing it. But you're saying that it should be faster if I duplicate the block, edit it off to the side, and then attach it later, right?
Definitely frustrating, and I hope this is something the developers are trying to improve.
Regarding the slowness during editting, is this because every time a change is made, Scratch automatically "recompiles" the script so it is ready for immediate execution? If so, would it be possible to add an option to allow the user to decide when to compile? I'd gladly trade off immediate execution ability for a less frustrating editing experience.
The Scratch Team is certainly fixing this in the next version of Scratch, which is a complete recode from the original.
I'm pretty sure Scratch recompiles the script whenever you add onto it, which results in the slowness of the program. Unfortunately, there is no simple way to turn off immediate compilation of the script - because one of the first goals of Scratch was to make it so there was no necessity to compiler or anything before running it, with even the ability to edit the project while it's running.
Offline