Phanthomphax wrote:

-snip-

And here's another idea:

clear [all v]

clear [this sprite v]

clear [other sprites v]

This is a pen block

I don't know if this was suggested, but I'll leave it here

switch to canvas: [canvas1 v] ::pen //allows you to switch to a particular canvas for editing
clear [canvas1 v] ::pen //clears selected canvas (also includes options all and current)
show canvas [canvas1 v] ::pen //would display selected canvas (also includes options all and current)
hide canvas [canvas1 v] ::pen //would stop displaying selected canvas (also includes options all and current)
bring [canvas1 v] to front ::pen //would shift the selected canvas to the front(also includes options current)
move [canvas1 v] to layer (1 v) ::pen //would reorder the canvases (also includes options current)

NitroCipher wrote:

Phanthomphax wrote:

-snip-

And here's another idea:

clear [all v]

clear [this sprite v]

clear [other sprites v]

This is a pen block

I don't know if this was suggested, but I'll leave it here

Kinda similar to this: https://scratch.mit.edu/discuss/topic/234935/

switch to canvas: [canvas1 v] ::pen //allows you to switch to a particular canvas for editing
clear [canvas1 v] ::pen //clears selected canvas (also includes options all and current)
show canvas [canvas1 v] ::pen //would display selected canvas (also includes options all and current)
hide canvas [canvas1 v] ::pen //would stop displaying selected canvas (also includes options all and current)
bring [canvas1 v] to front ::pen //would shift the selected canvas to the front(also includes options current)
move [canvas1 v] to layer (1 v) ::pen //would reorder the canvases (also includes options current)

NitroCipher wrote:

After scratch 3.0 is finished, will it be consolidated into one github repo? Or will it continue to be in scratch-gui, scatch-vm, scratch-blocks, scratch-render, etc. ?

getbent wrote:

TheMonsterOfTheDeep wrote:

only real 1.4 kids remember the waffles tag

sadly i'm not a real 1.4 kid

1.4 is the best version because you could have spaces in tags, plus you could have more than three of them xP

([variable v] :: variables)

stickfiregames wrote:

It's been a while since it was changed but I've just been reminded of it - what happened to these?

([variable v] :: variables)

Were they considered too confusing?

MegaApuTurkUltra wrote:

stickfiregames wrote:

It's been a while since it was changed but I've just been reminded of it - what happened to these?

([variable v] :: variables)

Were they considered too confusing?

It appears “hacked” set blocks are currently possible to create directly in the editor. But I don't see a way to do a get with indirection.

thisandagain please don't make us have to continue using () of ()?

([var or prop v] of [myself v]) // note that you can drop blocks in var-or-prop, as you've always been able to

MegaApuTurkUltra wrote:

stickfiregames wrote:

It's been a while since it was changed but I've just been reminded of it - what happened to these?

([variable v] :: variables)

Were they considered too confusing?

It appears “hacked” set blocks are currently possible to create directly in the editor. But I don't see a way to do a get with indirection.

thisandagain please don't make us have to continue using () of ()?

thisandagain wrote:

MegaApuTurkUltra wrote:

thisandagain please don't make us have to continue using () of ()?

Can you expand on this a bit? I'm not 100% sure I follow (still recovering from Scratch Day).

((variable-name) of [myself v])

thisandagain wrote:

MegaApuTurkUltra wrote:

stickfiregames wrote:

It's been a while since it was changed but I've just been reminded of it - what happened to these?

([variable v] :: variables)

Were they considered too confusing?

It appears “hacked” set blocks are currently possible to create directly in the editor. But I don't see a way to do a get with indirection.

thisandagain please don't make us have to continue using () of ()?

Can you expand on this a bit? I'm not 100% sure I follow (still recovering from Scratch Day).

MegaApuTurkUltra wrote:

((variable-name) of [myself v])

_nix wrote:

MegaApuTurkUltra wrote:

((variable-name) of [myself v])

By “myself” do you mean “(insert sprite name here)”, or do you mean the actual “myself” option that would select the sprite that is the caller of the block discussed here?

MegaApuTurkUltra wrote:

_nix wrote:

MegaApuTurkUltra wrote:

((variable-name) of [myself v])

By “myself” do you mean “(insert sprite name here)”, or do you mean the actual “myself” option that would select the sprite that is the caller of the block discussed here?

whatever works for you

point is, () of () is hacky and I don't like it. There needs to be a better way in Scratch 3

when I start as a clone
forever
if <([x position v] of [sprite1 v]) = (x position)> then // This is in sprite1
say [GET OFF OF ME!!!!!111!111!!!!!1!!!]
else
say [thanks for not stepping on me :D]

_nix wrote:

Phanthomphax wrote:

And also, a delete clones block

delete all clones

That's been suggested pretty much since clones were first introduced in 2.0 – it hasn't been implemented because there's a pretty simple workaround. Just make your sprites that get cloned have a when-I-receive that runs “delete this clone”, and use that broadcast to delete all of those sprites' clones.

when I start as a clone//put this in every sprite
forever
if <(DeleteClones) =[1]> then
delete this clone
end
end
define delete all clones
set [DeleteClones v] to (1)
wait (0.25) secs // makes sure that clones delete themselves
set [DeleteClones v] to (0)

Greenduck54 wrote:

_nix wrote:

Phanthomphax wrote:

And also, a delete clones block

delete all clones

That's been suggested pretty much since clones were first introduced in 2.0 – it hasn't been implemented because there's a pretty simple workaround. Just make your sprites that get cloned have a when-I-receive that runs “delete this clone”, and use that broadcast to delete all of those sprites' clones.

That wouldn't work.
This is a script that would work:

when I start as a clone//put this in every sprite
forever
if <(DeleteClones) =[1]> then
delete this clone
end
end
define delete all clones
set [DeleteClones v] to (1)
wait (0.25) secs // makes sure that clones delete themselves
set [DeleteClones v] to (0)

when I receive [delete clones v]
delete this clone

Phanthomphax wrote:

Greenduck54 wrote:

_nix wrote:

Phanthomphax wrote:

And also, a delete clones block

delete all clones

That's been suggested pretty much since clones were first introduced in 2.0 – it hasn't been implemented because there's a pretty simple workaround. Just make your sprites that get cloned have a when-I-receive that runs “delete this clone”, and use that broadcast to delete all of those sprites' clones.

That wouldn't work.
This is a script that would work:

when I start as a clone//put this in every sprite
forever
if <(DeleteClones) =[1]> then
delete this clone
end
end
define delete all clones
set [DeleteClones v] to (1)
wait (0.25) secs // makes sure that clones delete themselves
set [DeleteClones v] to (0)

His workaround does work. This is what it looks like:

when I receive [delete clones v]
delete this clone

Tested it and it works perfectly. But to be honest, it takes a lot of scripts for a simple clone delete rather than just one block which can do the job.

IcyCoder wrote:

Hmm what is this? https://github.com/LLK/scratchr2

IcyCoder wrote:

Hmm what is this? https://github.com/LLK/scratchr2