I'd like to be able to use the "x position of..." block, but I'd like to refer to the sprite containing the block. The pulldown menu should have an option called "me" or "self" or "this" or whatever your favorite self-reference is, to refer to the sprite containing the script.
Why?
Because Scratch doesn't have sprite cloning. The best I can do is create a prototype, edit all the costumes and scripts, and then duplicate it a bunch of times. Of course, once I've done that, I don't want to have to go into each individual sprite and find all the references to the original sprite and change them to the new sprite. Bleah.
If I can't have "me", then it would be nice when duplicating if the duplicator could recognize a reference to the original sprite and change it to be the new sprite.
More complex, but more useful:
Have a special sprite type that is a "duplicate of ____". That means that you can edit the original and all the duplicates suddenly get the new features you just edited. This is so when you make changes, you don't have to delete all the copies, then re-duplicate. You still need "me" for this one, though.
Offline
Just use the <x position>[/blocks] and <y position>[/blocks] blocks in the motion category. They do exactly what you're describing, unless I missed the point.
I really wish Scratch had sprite cloning. Sadly, they won't do it because new users would abuse the function, but there are people who've edited the source code to get those blocks.
Last edited by hmnwilson (2010-04-20 02:40:51)
Offline
Ha! I totally missed those, because I was looking in the Sensing category!
I still want a "duplicate of ______" sprite if I'm not allowed to have cloning, though.
Offline
hmnwilson wrote:
Just use the <x position>[/blocks] and <y position>[/blocks] blocks in the motion category. They do exactly what you're describing, unless I missed the point.
I really wish Scratch had sprite cloning. Sadly, they won't do it because new users would abuse the function, but there are people who've edited the source code to get those blocks.
It's mostly that we want Scratch to be super easy for new Scratchers - as described here: http://info.scratch.mit.edu/Suggestions_for_Scratch
So if we can find a way to make these concepts easy and intuitive (or at least not confusing) for Scratchers who are just starting out, maybe we could get this into Scratch 2.0. No promises though!
Offline