Ach! Stop requoting!!!

jrezneckbhds wrote:

SuperDragon2014 wrote:

I also think there should be a “delete unused variables” button so if, you, like me, forgot about lists and made like 50 variables you don't have to go through deleting EVERY SINGLE ONE.

I agree, but can't you always right-click them, and then delete them?

Yeah, you should see the big debate we had…

I think this would use up a lot of extra code for making Scratch and I cannot see many people using it. Sorry but I do not support.

MushroomMan99 wrote:

I think this would use up a lot of extra code for making Scratch and I cannot see many people using it. Sorry but I do not support.

To that I say that the image file for Scratch is just under 6 megabytes, which isn't that much so disk space is not a problem. And I can also say that other programs, like Netbeans, will tell you when a variable has not been used. So why can't Scratch do this as well?

MushroomMan99 wrote:

I think this would use up a lot of extra code for making Scratch and I cannot see many people using it. Sorry but I do not support.

1. Find all variables

2. Find all attached to a script with a hat block.

3. Those are used variables. All others are unused variables.


Come on. I don't really think it will make that much code.

Alberknyis wrote:

MushroomMan99 wrote:

I think this would use up a lot of extra code for making Scratch and I cannot see many people using it. Sorry but I do not support.

1. Find all variables

2. Find all attached to a script with a hat block.

3. Those are used variables. All others are unused variables.


Come on. I don't really think it will make that much code.

Yeah, I did research on that much code and it seemed to take up only 20-40 lines of code, maybe 50 or 60. That much code is only like less than a megabyte of storage…

peppermintpatty5 wrote:

Ach! Stop requoting!!!

There is no need to, if you have an argument to a certain post quote it…

RPFluffy wrote:

peppermintpatty5 wrote:

-snip-

There is no need to, if you have an argument to a certain post quote it…

You could cut out some of the quote, like I just did.
But anyway, I don't want this getting off topic.

support, though it should be desaturated, not grey.

Full support.

Implementation details or restrictions never should be an argument in evaluating user needs / requirements. It might only be an argument if the Scratch developers start thinking about how to implement it and come back to the users with a recommendation to not implement it because of technical considerations / limitations. However, I don't think this has happened already.