Scratch

for the "clone local" variables, I can think of a workaround, as long as the "clone #" reporter exists, also I think cloning a sprite would clone the sprites local variables too
The workaround:

when gf clicked
repeat (10)
add (pick random (1) to (3)) to [list v]
end
repeat (10)
clone
end
forever
set [personal local v] to (item (clone#) of [list v])

If there was no clone# block clones would be extremely limited, since they could only do things identically

At the time of this post, there is no clone number block. We NEED either a clone number block, or clone-local variables (preferably both), or clones will be extremely limited.

Last edited by joefarebrother (2012-10-12 16:28:57)

this could be confusing to new users which would then defeat the purpose of scratch

clone-local variables would be useful although i dont fully know what happens with cloning. that may have even been implemented already

Wes64 wrote:

this could be confusing to new users which would then defeat the purpose of scratch

clone-local variables would be useful although i dont fully know what happens with cloning. that may have even been implemented already

If you're referring to 5 different variable types, agreed.
if you're talking about having a "clone #" block, I can hardly see how it would be confusing, and without it the only workaround I can think of requires very specific timing if you want clones to react the way you want them to

zammer990 wrote:

Wes64 wrote:

this could be confusing to new users which would then defeat the purpose of scratch

clone-local variables would be useful although i dont fully know what happens with cloning. that may have even been implemented already

If you're referring to 5 different variable types, agreed.

thats what im talking about. 

joefarebrother wrote:

That's what I originally thought of, but what i there wasn't a "clone number" reporter?

You make it.

when gf clicked
set (clone # v) to (0)
delete (all v) of (clone vars v)
repeat (10)
  change (clone # v) by (1)
  clone
  add (pick random (1) to (3)) to (clone vars v)
end

(item (clone #) of (clone vars v)) //then, to retrieve the values

Hey, Scratch is all about making stuff simple for kids and people just getting into programming, but one big aspect of programming is coming up with practical solutions to whatever you need to do. 

I agree that Scratch needs "temporary" or "local" variables, they're useful for iterators and the such. Projects tend to get quite messy if you need lots of these. 

Last edited by technoguyx (2012-10-13 11:25:41)

technoguyx wrote:

joefarebrother wrote:

That's what I originally thought of, but what i there wasn't a "clone number" reporter?

You make it.

when gf clicked
set (clone # v) to (0)
delete (all v) of (clone vars v)
repeat (10)
  change (clone # v) by (1)
  clone
  add (pick random (1) to (3)) to (clone vars v)
end

(item (clone #) of (clone vars v)) //then, to retrieve the values

And how do the clones identify themselves on the list once the variable changes for the next clone?

technoguyx wrote:

I agree that Scratch needs "temporary" or "local" variables, they're useful for iterators and the such. Projects tend to get quite messy if you need lots of these. 

Yeah. Either that or you try to recycle them for different scripts but then you have to end up giving them generic names like "temp" or "value" and it makes your project hard to read. Or BOTH happen. 

Last edited by joefarebrother (2012-10-13 13:10:14)

Borrego6165 wrote:

i'm sure there clone-local variables, like on Panther there were.

At the time I made this topic, local variables worked like the sprite-local variables I described above, that all clones of one sprite use the same variable.

kayybee wrote:

Currently, if a sprite with a local variable clones, a new clone-specific variable will be created.

At the time of making this topic, that wasn't what happened.

kayybee wrote:

joefarebrother wrote:

kayybee wrote:

Currently, if a sprite with a local variable clones, a new clone-specific variable will be created.

At the time of making this topic, that wasn't what happened.

Let me test again...

EDIT: clone-specific variables are created when a sprite is cloned with a local variable. that's how my score works (a sprite with costumes 0-9, and clones to match a digit of a variable). where are you getting you information from, that it does not do that?

It's what happened when I tested it before making this topic.

kayybee wrote:

joefarebrother wrote:

kayybee wrote:

Let me test again...

EDIT: clone-specific variables are created when a sprite is cloned with a local variable. that's how my score works (a sprite with costumes 0-9, and clones to match a digit of a variable). where are you getting you information from, that it does not do that?

It's what happened when I tested it before making this topic.

You're a tester? Oh. Never saw you on the forum.
But it's always been the way I described, so I don't know if you we're doing something differently. Look at my project the billion button. Look inside it and you'll see that each digit has its own variable. Or my particle test. The most recent one with gravity. The gravity wouldn't work if they all had the same variable...

I'm not a tester, I've just read this. At some point before I made this topic I did a test and local variables worked as sprite-specific, not clone-specific.