Replies: 1 comment 1 reply
-
@jdonwells this is great feedback, I would love an issue or pull request on how you think it should be worded. Would love to see how you resolved this so we could incorporate it. Andrew |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Part 2.2 says "What happens to the original ("master") sprite each time the spacebar is pressed? Does that seem useful? What role should the original sprite play now that we're cloning?"
What is this getting at? Sprites in Snap! like objects in Javascript use a prototype instead of a class. Is that what this is about?
The bonus says "Assign each clone a different value for some properties, such as speed, color, or size. Try controlling these values from the master sprite rather than having each clone choose its own." Why would I do that in a prototyping language?
As far as I can tell the original sprite is special in that it does not show up in the my clones block. So if the original sprite (I don't think I would call it master sprite) uses my clones it shows all of the clones, but if a clone uses my clones it shows the clones minus itself and minus the original sprite.
Beta Was this translation helpful? Give feedback.
All reactions