I know people probably have encountered this: When creating a long list of local variables, they need to change the check mark that tells which type of variable to local. Than, when it gets created, it automatically shows on the screen. What if Scratch remembered the last type of variable you used and whether it was visible? Than, you can create a long list of local variables twice as fast (more or less).
Offline
good idea I don't make too much local variables but when I do it would help. But when it automatically shows up that is just plain annoying.
Offline
mrguy740 wrote:
good idea I don't make too much local variables but when I do it would help. But when it automatically shows up that is just plain annoying.
I hate that it does that too! And I use local variables a lot, like in this game I am making (for fun. Not like Draw your character), I had to use local variables to remember the costumes. It was a pain in the rear ( ) to have to check and uncheck and click loacal
Offline
I guess a mechanism that recalls your last choice (if the variable is local or global and if you want it on the stage) would save a lot of time. I think they behave as they do now just to make it very simple to young programmers. An environment that does behave always the same way is much simpler to learn.
Offline
i wish you could change a variable from local to global after it was created as sometimes you realise you have to change it.
Offline
bigB wrote:
i wish you could change a variable from local to global after it was created as sometimes you realise you have to change it.
That would also be good too
Offline