Scratch

I would rather have a block that could enable/disable turbo speed.

Either make it a container:

+-- Turbo speed ---
|
| (blocks you want to go fast)
|
+-------------------------


or something global (that accepts a variable input):


[ Turbo mode [ Enable   v] ]

and a reporter

<turbo mode?>


As it is today, I need my Tower Defense game requires turbo mode.  So, I had to make a turbo mode detector for it.

Last edited by BoltBait (2011-07-22 18:58:06)

Turbo speed, as you may find after using it for a while, is not necessarily simply letting Scratch run at maximum potential. I don't know exactly how it works, but it tends to result in less precise movement and bugs that wouldn't occur in a project running at regular speed.

You should also remember that some languages that are slower than others. Scratch, being a visual language on top of a high-level language and running in a virtual machine is inherently slow.

However, it is known that there is a slight delay built into loop blocks to make movement of sprites easier. It has been requested there be an option to remove this feature when scripting things that are only slowed down by this, which is an idea I support.

what? WHAT?! So because you are angry at something, you want everybody else's way changed to fit yours? Dude, just click an extra button.

...Not that hard...

cygene wrote:

It took me an hour to find the change single stepping button under the edit heading. (don't remove flash blocks, though, that is a vital process in program troubleshooting).

It took me ten minutes after downloading Scratch, and even if you couldn't find it, you could ask people on the forums.  And if they're going to remove everything else, then they should remove single stepping.  I happen to like turbo mode, but a lot of games still run better without it.

Actually single-stepping isn't the default setting in Scratch - you need to click on the "Edit" option in the menu bar and select the option from the drop-down menu to start single-stepping. Otherwise, projects will run at normal speed. 

Single-stepping is in Scratch as a means to try and catch programming bugs in projects, which is why the slowest setting is used by default. Other programming language interfaces have similar functions to single-step through code as a way of debugging (Visual Studio for building C++ is a good example), perhaps that is where the inspiration for the single-step function comes from. I've used single-stepping to debug through my Scratch projects at times. Whether or not the Scratch developers want to set turbo speed single-stepping as the default speed that is their decision, but I think the benefits for single-stepping outweighs taking it out completely. 

Single stepping (slow) is for debugging, turbo speed is for evaluating difficult code, etc.
I disagree.

I'm not sure what single stepping is, but I'm just going to assume you're thinking what I am.

There's an easy fix:

So, let's say you want a sprite to glide from here to there, and at the same time switch its costumes. you can do this:

When Flag Clicked
Go to here
Broadcast multitask

When I recieve multitask
Glide _ seconds to there

When I recieve multitask
Repeat _ times
Next costume.

I don't know how this relates to turbo though ^^;
But in my experience, turbo only works on pen projects.

But think about an animation. It would almost be not viewable on turbo.

scimonster wrote:

But think about an animation. It would almost be not viewable on turbo.

unless you time it with wait blocks. Anything can be made to run perfectly in turbo speed! Why would all other programming languages run really fast if there was a reason not to?

cygene wrote:

scimonster wrote:

But think about an animation. It would almost be not viewable on turbo.

unless you time it with wait blocks. Anything can be made to run perfectly in turbo speed! Why would all other programming languages run really fast if there was a reason not to?

Then people would have to change all their animations without that...

kayybee wrote:

cygene wrote:

scimonster wrote:

But think about an animation. It would almost be not viewable on turbo.

unless you time it with wait blocks. Anything can be made to run perfectly in turbo speed! Why would all other programming languages run really fast if there was a reason not to?

Then people would have to change all their animations without that...

Well, you could make Scratch's current normal speed as a selectable option, and turbo speed would be dafault

You're suggesting this now? There are almost 2 million projects built to run in normal speed. If the Scratch Team took up your suggestion, most of them would be unplayable unless everyone manually changed all their projects to run in turbo mode.

Besides, just using the wait block could be considered "bad programming", because many languages don't even have that, and you must set up your own timers instead. As long as the wait block stays, so should normal speed.