In the looks category the block
switch to costume [costume v]allows reporter blocks to be put inside.
switch to costume <<costume #> - (1)>I think more blocks should allow reporter blocks inside of them too. List your suggestion of blocks that should have them with a reason
<key [space v] pressed?> //would need a report like "space" coming from the reporter block
<key <item (1 v) of [list v]> pressed?> //would be an example of a useThat one so that you could have customizable controls in games without needing a lot of if's and copying.
set [variable v] to [] //would need either the circle of the variable nested or a report of the wanted variable name
set <item (1 v) of [list v]> to [] //would be an example of a useneeded because you might need to change which variable you are going to change.
Supporters: 20
TorbyFork234
schusteralex2
Jonathanpb
ftf841
SplatKirby
MoreGamesNow
gettysburg11
pi3
mythbusteranimator
360-International
technoboy10
Mokat
coolhogs
RedRocker227
Chrischb
PullJosh
veggieman001
G0D_M0D3
scimonster
James07
Last edited by TorbyFork234 (2012-06-07 13:06:01)
Offline
bump
Offline
@coolhogs I searched "tesseract" on google, and I got an animated GIF of a tesseract, pretty convenient if you ask me...
Offline
I support.
Offline
Add meeee!
Offline
bump
Offline
bump
Offline
la bump
Offline
I support.
Just one more thing: How about making more "broadcast" blocks? such as
when gf clicked repeat until < i receive [stop] > turn cw (3) degreesYou can do a separate script, or create a ton of variables, but this would make it a lot easier. Plus, a separate script paired with a "forever" block in another script glitches like crazy.
Offline
mythbusteranimator wrote:
I support.
Just one more thing: How about making more "broadcast" blocks? such as
when gf clicked repeat until < i receive [stop] > turn cw (3) degreesYou can do a separate script, or create a ton of variables, but this would make it a lot easier. Plus, a separate script paired with a "forever" block in another script glitches like crazy.
This was just another suggestionfor a new block.
I always use variables. Instead of the
broadcast [broadcast v]block, I just use set variable to 1 stuff. There really isn't a difference.
Offline
I definitely support this.
Offline
Support!
On a side note, I wouldn't expect any of those to be too difficult to code (but then again, I don't know squeak )
Offline
Support, variable inserts are very very very useful
Offline
TorbyFork234 wrote:
mythbusteranimator wrote:
I support.
Just one more thing: How about making more "broadcast" blocks? such as
when gf clicked repeat until < i receive [stop] > turn cw (3) degreesYou can do a separate script, or create a ton of variables, but this would make it a lot easier. Plus, a separate script paired with a "forever" block in another script glitches like crazy.
This was just another suggestionfor a new block.I always use variables. Instead of the
broadcast [broadcast v]block, I just use set variable to 1 stuff. There really isn't a difference.
Where is i recive __________?
Offline
James07 wrote:
TorbyFork234 wrote:
mythbusteranimator wrote:
I support.
Just one more thing: How about making more "broadcast" blocks? such as
when gf clicked repeat until < i receive [stop] > turn cw (3) degreesYou can do a separate script, or create a ton of variables, but this would make it a lot easier. Plus, a separate script paired with a "forever" block in another script glitches like crazy.
This was just another suggestionfor a new block.I always use variables. Instead of the
broadcast [broadcast v]block, I just use set variable to 1 stuff. There really isn't a difference.Where is i recive __________?
It's a block that s/he wants.
Offline