My idea :

when [variable v] clicked ::variable hat //category=variables
set [variable v] size to [] //category=variables

Oh my! This is meant to be in suggestions! Whoopsies. I thought I was on suggestions forum

ZozaTech wrote:

Oh my! This is meant to be in suggestions! Whoopsies.

Moving to Suggestions….

Interesting. How would this block work though? I can see a few situations in which it could be useful but other than those, it doesn't seem to have too many uses. Semi-support.

Nether_before wrote:

Interesting. How would this block work though? I can see a few situations in which it could be useful but other than those, it doesn't seem to have too many uses. Semi-support.

People make quizzes, and they have to make buttons. Why waste time when you can resize the variable(with the block I suggested) and be able to code what will happen when clicked?

ZozaTech wrote:

People make quizzes, and they have to make buttons. Why waste time when you can resize the variable(with the block I suggested) and be able to code what will happen when clicked?

Hmm, I can see other uses for this as well:
Creating an inventory screen
loading a help tip for your variable
testing a movement script idea

But, most of the uses could be workarounded by making your own buttons to change the variable, so I still Semi-Support.

Support.

Semi-support.

TheAwesomeMaster wrote:

Semi-support.

Why?
80% support, although it will definitely be handy, it doesn't seem to have many uses.

I support this, because having variables upsize and shrink would help unclutter. Maybe they should also introduce a colour changer for variables as well. Browny-orange is a bit… eugh.

Semi-support as per-

Nether_before wrote:

Interesting. How would this block work though? I can see a few situations in which it could be useful but other than those, it doesn't seem to have too many uses. Semi-support.

Nether_before wrote:

ZozaTech wrote:

People make quizzes, and they have to make buttons. Why waste time when you can resize the variable(with the block I suggested) and be able to code what will happen when clicked?

Hmm, I can see other uses for this as well:
Creating an inventory screen
loading a help tip for your variable
testing a movement script idea

But, most of the uses could be workarounded by making your own buttons to change the variable, so I still Semi-Support.

Support! This would be a useful feature

Support! The most recently featured project could use this to prevent cheating… Am I too late here?

bump

bump

bump cause dupe
ninja'd :/

support

pythonicKI wrote:

support

why do you support? in the forums you have to be constructive.

the_awsome_penguinja wrote:

(#18)

pythonicKI wrote:

support

why do you support? in the forums you have to be constructive.

not trying to be rude but a lot of people just write ‘support’ or ‘+1’
I support because I feel it would be a lot easier to manipulate the variable output rather than to get a text engine/get a whole bunch of number costumes

pythonicKI wrote:

not trying to be rude but a lot of people just write ‘support’ or ‘+1’

yeah and that's the problem, we can't just say “+1” or “support” without reasoning, or there really isn't any point to adding it.
it's also kind of unconstructive