Hi. I just wanted to point out that there's no need for <next costume> because it can easily be replaced with <switch to costume[ (( <costume# <+> 1 ))
Last edited by martianshark (2009-09-21 01:00:03)
Offline
I know that, and so do lots of people.
But there's some points I'd like to make,
1. It's fast in animations and such. You just reach into the Looks pallette, and drag a block.
2. New users would easily get tired of having to continuously reach for the required blocks.
3. It's nice having at least one block to use.
You can reply on those points if you like.
Offline
I didn't mean that it was bad, I just meant that there's no need for it.
Offline
martianshark wrote:
I didn't mean that it was bad, I just meant that there's no need for it.
I know.
Offline
Yes there is also no need for
<move( )steps>
<go to[
<when[ ]key pressed>
<forever if>
<distance to[
These blocks are all easily replaced by others
Offline
archmage wrote:
Yes there is also no need for
<move( )steps>
<go to[
<when[ ]key pressed>
<forever if>
<distance to[
These blocks are all easily replaced by others
I don't see hov <move( )steps> can be replaced.
Last edited by The-Whiz (2009-09-21 16:29:56)
Offline
The-Whiz wrote:
archmage wrote:
Yes there is also no need for
<move( )steps>
<go to[
<when[ ]key pressed>
<forever if>
<distance to[
These blocks are all easily replaced by othersI don't see hov <move( )steps> can be replaced.
Yes... <move( )steps> is not the same thing as <change x by( or <change y by( if your angle, for example is 37. (the direction you're pointing.
Offline
Move steps is the same as
change x sin of direction* # of steps
change y cos of direction* # of steps
But like next costume it exists because it is simpler to have move # steps
Last edited by archmage (2009-09-21 18:00:16)
Offline
archmage wrote:
Move steps is the same as
change x sin of direction* # of steps
change y cos of direction* # of steps
But like next costume it exists because it is simpler to have move # steps
Yeah, newer members aren't likely to know that.
Offline
Newer member aren't likely to know that go to costume (costume# + 1) is the same as next costume either.
Offline
Like a variable, have "switch to costume ______" and "change costume by ______"
Offline
Bentheneighbor wrote:
Like a variable, have "switch to costume ______" and "change costume by ______"
[switch to costume (1)] = [set [costume] to [1]] [switch to costume (costume)] [change costume by (5)] = [switch to costume ((costume #) + (5))]
Offline
archmage wrote:
Yes there is also no need for
<move( )steps>
<go to[
<when[ ]key pressed>
<forever if>
<distance to[
These blocks are all easily replaced by others
Even if they're not neccessary, they're still handy... no need to assemble a group of blocks, and some people wouldn't know how to do some of them.
Offline
Shouldn't this be moved to All About Scratch? After all, this isn't suggesting anything. And it isn't telling people "There's no need to suggest this!", because these blocks already exist.
Offline
archmage wrote:
Move steps is the same as
change x sin of direction* # of steps
change y cos of direction* # of steps
But like next costume it exists because it is simpler to have move # steps
I used that method for directional movement in one of my projects
Offline
weswesrock wrote:
archmage wrote:
Move steps is the same as
change x sin of direction* # of steps
change y cos of direction* # of steps
But like next costume it exists because it is simpler to have move # stepsI used that method for directional movement in one of my projects
I just used that in my newest project...
Offline
It's easier to have a block for changing to the costume, I know it can be replaced by other blocks but so can other things.
Like
Point towards
It could be replaced with a trigonomentric function, look at scmb1:s stuff and see.
Last edited by jacool (2009-09-25 10:58:23)
Offline
We also don't need:
[blocks]<turn cw( )degrees>
<go to[
<wait until>[/blocks]
Offline
There's also no need for:
[blocks]
<timer>
<reset timer>
<( <<> )>
(( <-> ))
[/blocks]
Offline
We need both greater than and less than and the minus block can be done without but that would be too much of a pain.
Offline
The-Whiz wrote:
We don't need
<change{ Variable }by( 1
Or
<say[ Hello ]for( 1 )secs>
Or
<think[ Hello ]for( 1 )secs>
weswesrock wrote:
There's also no need for:
[blocks]
<timer>
<reset timer>
<( <<> )>
(( <-> ))
[/blocks]
Yes we do.
Last edited by fruit (2009-09-25 19:10:49)
Offline
No need for
<set x to( 0
<change x by( 10
<set y to( 0
<change y by( 10
fruit wrote:
The-Whiz wrote:
We don't need
<change{ Variable }by( 1
Or
<say[ Hello ]for( 1 )secs>
Or
<think[ Hello ]for( 1 )secs>weswesrock wrote:
There's also no need for:
[blocks]
<timer>
<reset timer>
<( <<> )>
(( <-> ))
[/blocks]Yes we do.
How so?
<set{ Variable }to( (( Variable <+> 1 ))
<say[ Hello
<wait( 1 )secsc>
<say[
<think[ Hello
<wait( 1 )secsc>
<think[
Use a simple timer script.
<not> <( 2 <>> 1 )> >>
(( 1 <+> -1 ))
Last edited by The-Whiz (2009-09-25 19:16:14)
Offline