Scratch
archived forums
#1 2009-07-16 15:55:14
New Blocks
here are some blocks i would like to see (next to them is where they are):
[previous background] looks
[previous costume] looks
[set text font to ___] looks
[set text size to ___] looks
[record for _ seconds] sound
[play back for _ seconds] sound
[go ahead _ costumes] looks
<___ effect equals _> looks
[stop if ___] control
[repeat for _ seconds] control
[play sound for _ seconds] sound
[if on edge stop] motion
[stamp mouse pointer] pen
[change ___ effect for _ seconds]
[set vibrate effect to _] looks (incase you didnt know, it makes the sprite look like it is shaking and the higher the number you put in, the faster.)
Last edited by wiimaster (2009-07-17 09:11:40)
Offline
#3 2009-07-16 18:58:24
- EternalEphemeral
- Scratcher
- Registered: 2009-06-09
- Posts: 6
Re: New Blocks
[stop if __] is useless. its the same thing with <if>something<stop script><end>
Offline
#5 2009-07-16 23:18:59
Re: New Blocks
Previous background/costume can be solved by using:
[switch to background [(background) - (1)] ]
[switch to costume [(costume) - (1)] ]
[Set text size or font to (___)] is different... the good news is that you shouldn't need too many different sizes or fonts in a sprite, unless you want to change them both in the same one (or you're making Microsoft Word).
The sound blocks are different too; for the first, are you talking about it remembering what sound is being played? If so, there's nothing to do.
The other one hard also... playing the music backwards is a difficult case. The best solution is to have an alternate sound that has been altered (use Audacity or something similar). The problem is, you need to make a different sound edit for each second (each second could be the one that gets played back, you never know). That makes that block terrifying.
The [go ahead for (__) costumes] block can be done:
[switch to costume [(costume) + (whatever you want)] ]
The <(__) effect equals (__)> block can be done too, but with more effort. Assign a variable to change the effect you like. This is tedious, though; you have to change the variable after every time the effect is changed. The easy bit is to script:
..........
forever
if <(variable) = (the required number)>
[do what you like here]
The [stop if] block can be done as said earlier:
..........
forever
if <what stops the project>
stop script (or stop all)
The [repeat for (__) seconds] block is possible too; just have the timer at 0 (reset timer block neccessary)
..........
repeat until <(timer) = (number)>
[do what you like]
[reset the timer here if neccessary]
Hope this helps!
I fall: It's a tragedy. You fall: It's comedy.
Hmph enjoy your fall - I get a lovely spring... without pans of new leaves.
Offline
#8 2009-07-17 05:40:53
Re: New Blocks
Filo5, that's a tricky one. The most you can do is to have a sprite that covers up the list, but it has to look the same as the background. This can't be done if the background changes repeatedly and randomly, but it will work with simpler projects.
But those blocks would be nice...
I fall: It's a tragedy. You fall: It's comedy.
Hmph enjoy your fall - I get a lovely spring... without pans of new leaves.
Offline
#10 2009-07-18 09:59:33
Re: New Blocks
Chrischb wrote:
Filo5, that's a tricky one. The most you can do is to have a sprite that covers up the list, but it has to look the same as the background. This can't be done if the background changes repeatedly and randomly, but it will work with simpler projects.
But those blocks would be nice...
I've made a tutorial on doing that...
Also, I know that some of those blocks can be scripted, but wouldn't it be easier to just have blocks? But then the Scratch community would become dependant on blocks to do everything...
Offline
#11 2009-07-20 01:33:29
- AquinPlace
- Scratcher
- Registered: 2009-07-16
- Posts: 1
Re: New Blocks
I don't know if this stuff exists or whether I'm missing something....
But it'd be great to add "tags" to objects. So you can sense "when touched by an object containing <tag>" and react to it.
That way I can tag all my bullets and not have to have individual broadcast messages on all of them.
Creating and destroying objects would be nice too, but that's probably asking too much.
Offline