This is still relevant in 2020, so I'll go ahead and bump it.

support

squarepoint wrote:

support

Why do you support?

I only looked this up to get the answer, so can yall do yo job

I support I've needed to do this 100s of times(literally not figuratively).

Support.

Support

Support!! I think the “rename variable/list” option should be replaced with “edit variable/list” and it would work the same as editing a custom block.

support!

Support. Then you don't have to delete a bunch of data.






5uper idea!

Bump off the 2nd page!

codethelife wrote:

set [cool] to [for all sprites]

set [cool] to [this sprite only]

Don't blockspam. Oh, that's the answer???

DaSpudLord wrote:

Support, but what would happen if the variable is being used in multiple sprites?

I think all the reporters of that once-global variable in other sprites would turn into

([local v] of [sprite1 v]) 

when it turns local. I also think that the drop-down for the existing variable stacks should change to the first variable in the palette of that sprite instead of all those blocks just getting deleted when you both edit and delete a variable. Only when there's no variables left for a sprite should all those blocks get deleted.

So much support, how did I never see this?
If you feel like you should change a variable to all sprites, it's a pain in the !*#& [totally meant “butt” right there] to have to replace every variable. I think you should be able to right click it in the palette and select the option to do so.

wow, like you post the question I literally just answered or say something I just proved my point against so many times XDDD

edit: not that many times :P

IndianRuby718 wrote:

DaSpudLord wrote:

Support, but what would happen if the variable is being used in multiple sprites?

I think all the reporters of that once-global variable in other sprites would turn into

([local v] of [sprite1 v]) 

when it turns local. I also think that the drop-down for the existing variable stacks should change to the first variable in the palette of that sprite instead of all those blocks just getting deleted when you both edit and delete a variable. Only when there's no variables left for a sprite should all those blocks get deleted.

K, makes sense

Sheep_maker wrote:

In Scratch 2.0, you could delete a variable and recreate it with the proper setting without deleting the blocks that use it.

Scratch 3.0 tried to be smart by deleting corresponding blocks when you delete a variable, but one way around this is to put the scripts in your backpack, delete and recreate the variable, then drag the scripts back out.

That would be a great if my project didn't already have more than 1850 individual blocks which are about 95 individual scripts that would have to go into the backpack and then brought back out and they would all be on top of each other and then I could do the “Clean Up Blocks” thing but then they would not be where I remember them to be lol

Hearst10 wrote:

support!

because

-CloudGate- wrote:

I've needed to do this 100s of times(literally not figuratively).

I absoulutley agree!

change [foo v] to [for this sprite only v]::variables

no support, just recreate the variable