| Languages: |   |
 |
 |
 |
 |
You do not have any products in your shopping cart yet. Shopping Cart » |
Quick purchase
Please enter the article number from our catalogue.
More about...
Informations
Reviews
Newsletter Subscribing!
Info
Customer group:Guest
Manufacturer
Reviews to:
Date: Monday, 28. July 2014
Author: Gast
Reviews to:
Review:
Hi Natalie,I see, what you refer as sprite sheet (.h and .m) is what we nolmarly call a class. Yes, I would recommend to make each sprite type its own class handling its own touches. So if you have kids and teachers, you would make two classes, a teacher class and a kid class. That all depends on what type of behavior you want. I am supposing above that teacher behaves differently from kids, and that the kids behave similar to each other. But if it is not so, for instance the girls behave differently from the boys, then you would have three classes. Suppose that the girls behave 90% as the boys do and 10% differently. Then you would make a kids class, and subclass it into two subclasses, boys class and girls class. the same behavior would go into kids class and the different behavior would go into girls class and boys class. For instance in the GalaxyFighter course there is a FlyManager class, where I collect all the behavior that is common among the flying objects like, MeteorManager, AlienManager, PlanetManager and so on. Study that code carefully and you will see the possibilities!thanksBob
Evaluation:
