Scratch

maybe a delete sprite block

techy wrote:

maybe a delete sprite block

and a duplicate sprite block although this would be hard for the scratch time to implement

how about when enter key pressed.

there needs to be a text box feature when you are making a sprite. importing each letter can become tiresome.

[blocks]
<when[ Object ]clicked>
<if><mouse down?>
<say[ Left
<else>
<say[ Right
[/blocks]

ScratchScripter wrote:

[blocks]
<when[ Object ]clicked>
<if><mouse down?>
<say[ Left
<else>
<say[ Right
[/blocks]

Yeah that is the best way to right/left click sense that I know of.

This is now the top replied to thread in the suggestion forum! 

Last edited by demosthenes (2009-01-15 21:06:13)

TheComedian wrote:

do a duplicate sprite block :-)

Cloning has been suggested an immeasurable amount of times. I doubt Scratch will ever implement it as new users would just mess around with and create problems, unless, of course, there was a limit to the amount of cloned sprites you could create.

the next version will most likely not be called 1.4... maybe something like 1.3.2 or 1.3.1.1. ya never know, ya know?

A TRUE platforming Stage Script. Also Platformer Templates, and the ability to build FULL RPGs.
Also a way to use Raiden-Fighter-esque Lasers

there should be an <i recieve [ ]> block

BlueFlame wrote:

I have another idea... Everyone says: 'What about an [<any> key pressed] block.' I agree with this, BUT I think it would also be a good idea to have a [<letter> key pressed] and a [<number> key pressed] block. This would be useful for games where only the letter keys are involved.

Or a varible for key pressed. (A.k.a [Letter] or [KeyPressed] ) then you could have a block for varibles that looked this this ( [] = anything )

Spenfen wrote:

and set width too, of course. And, to all of those people who don't know: YES. ARRAYS WILL BE INCLUDED IN 1.4.

Just a question: What's different between a list and an array? I can't think of any.


Also, I thought of a good block for 1.4:
  set variable to [true]
A true/false variable! You could do that instead of using [0] as false and [1] as true. Convenient or what?

Or, another function:
  switch [variable]
This could be another part of the true/false variable.  It would be used to switch the true/false variable instead of saying:
  if <variable=[false]>:
  variable=[true]
And that reversed, like this:
  if <variable=[true]>:
  variable=[false]

More blocks for 1.4 or future:
(Note: If I put a "/=" in there, I mean the Dose Not Equal sign.)
  record for (10)secs
  play [recording1]
  <( ) /= ( )>
  _________________________________
  |when I receive [broadcasted text]|
  ||say (Hey, I just received something through a NON-SCRIPTSTARTER block!!!)
  |________________________________|
  This isn't a block, but they somehow make a text input on the stage and have it be able to be compared?