Scratch

juststickman · 2010-05-29 03:59:59

I think we should improve loop blocks...

First of all, remove the time delay in them. Repeat blocks run MUCH more slowly than forever blocks.

Second, make everything be executed in a loop before the program runs every loop again. Example: you have a repeat until block inside a forever loop, and a forever loop. The second forever loop will do whatever it's doing faster than the first. So we should remove this (with the exception of forever loops and loops including wait blocks).

coolstuff · 2010-05-29 09:20:33

I agree. I've found I have to duplicate what's inside of the loops to make them work faster.

Loops should work as fast as if the blocks were repeated multiple times, but without having to do so.

shadow_7283 · 2010-05-29 19:26:06

I completely agree. Loops can be such a pain...

iCode-747 · 2010-05-29 19:35:05

I agree 100%.

This should be a priority for Scratch 2.0.

MathWizz · 2010-05-30 20:29:18

iCode-747 wrote:
I agree 100%.

This should be a priority for Scratch 2.0.

Lets make a correction:

This should the BIGGEST priority for Scratch 2.0.

fg123 · 2010-05-30 20:35:04

No. The second biggest. The first is SHOW/HIDE blocks. wink

MathWizz · 2010-05-30 20:38:04

fg123 wrote:
No. The second biggest. The first is SHOW/HIDE blocks.

You mean the show/hide list blocks?

iCode-747 · 2010-05-30 21:39:07

MathWizz wrote:
fg123 wrote:
No. The second biggest. The first is SHOW/HIDE blocks.
You mean the show/hide list blocks?

Yeah, that should be up there.

I'd also love to see an 'execute together' loop block.

It would execute the blocks together simultaneously! smile

coolstuff · 2010-05-30 21:47:47

iCode-747 wrote:
MathWizz wrote:
fg123 wrote:
No. The second biggest. The first is SHOW/HIDE blocks.
You mean the show/hide list blocks?
Yeah, that should be up there.

I'd also love to see an 'execute together' loop block.

It would execute the blocks together simultaneously!

Really? That's what an execute together block would do? yikes
big_smile I support all the ideas on this thread, but keep it on-topic, guys.

Jonathanpb · 2010-05-31 01:55:21

I support 100%! big_smile

juststickman · 2010-06-17 11:52:37

Bump. If anything, this is the one update I want in scratch.
Seriously.... This would mean the following things would be possible:
-Infinite amounts of projectiles with 1 sprite
-Tower defense games
-First person shooters (slow, limited ones though)

coka · 2010-06-17 15:47:09

Great idea! tongue

archmage · 2010-06-17 15:58:16

juststickman wrote:
Bump. If anything, this is the one update I want in scratch.
Seriously.... This would mean the following things would be possible:
-Infinite amounts of projectiles with 1 sprite //Increased yes, infinite, not even close. Being able to dupe sprites is still needed to actually have many sprites
-Tower defense games //Maybe, but dupe blocks would make it possible probally
-First person shooters (slow, limited ones though) //It would speed up the 3D rendering process but it would still be too slow to make anything great

The loops in scratch are this way on purpose, you don't just code things and get this sort of delay automatically. The lag helps in things like movement and costume changing. But it makes anything you want to process quickly much much slower.

I rember posting a top 10 most needed improvements and this was #2 below sprite duping.

juststickman · 2010-06-17 16:03:14

archmage wrote:
juststickman wrote:
Bump. If anything, this is the one update I want in scratch.
Seriously.... This would mean the following things would be possible:
-Infinite amounts of projectiles with 1 sprite //Increased yes, infinite, not even close. Being able to dupe sprites is still needed to actually have many sprites
-Tower defense games //Maybe, but dupe blocks would make it possible probally
-First person shooters (slow, limited ones though) //It would speed up the 3D rendering process but it would still be too slow to make anything great
The loops in scratch are this way on purpose, you don't just code things and get this sort of delay automatically. The lag helps in things like movement and costume changing. But it makes anything you want to process quickly much much slower.

I rember posting a top 10 most needed improvements and this was #2 below sprite duping.

I know they are this way on purpose, so I'm asking that they're not made this way.

Would it be possible to hack a block that doesn't have the delay?

Scratch

archived forums

#1 2010-05-29 03:59:59

Improving loops (AKA making them faster and changing timing)

#2 2010-05-29 09:20:33

Re: Improving loops (AKA making them faster and changing timing)

#3 2010-05-29 19:26:06

Re: Improving loops (AKA making them faster and changing timing)

#4 2010-05-29 19:35:05

Re: Improving loops (AKA making them faster and changing timing)

#5 2010-05-30 20:29:18

Re: Improving loops (AKA making them faster and changing timing)

iCode-747 wrote:

#6 2010-05-30 20:35:04

Re: Improving loops (AKA making them faster and changing timing)

#7 2010-05-30 20:38:04

Re: Improving loops (AKA making them faster and changing timing)

fg123 wrote:

#8 2010-05-30 21:39:07

Re: Improving loops (AKA making them faster and changing timing)

MathWizz wrote:

fg123 wrote:

#9 2010-05-30 21:47:47

Re: Improving loops (AKA making them faster and changing timing)

iCode-747 wrote:

MathWizz wrote:

fg123 wrote:

#10 2010-05-31 01:55:21

Re: Improving loops (AKA making them faster and changing timing)

#11 2010-06-17 11:52:37

Re: Improving loops (AKA making them faster and changing timing)

#12 2010-06-17 15:47:09

Re: Improving loops (AKA making them faster and changing timing)

#13 2010-06-17 15:58:16

Re: Improving loops (AKA making them faster and changing timing)

juststickman wrote:

#14 2010-06-17 16:03:14

Re: Improving loops (AKA making them faster and changing timing)

archmage wrote:

juststickman wrote:

Board footer