Is it bad to have more than one CCTimer running? The most I’ve ever seen is two, and I’m wondering if it’s bad practice to have more than that.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it bad to have more than one CCTimer running? The most I’ve ever seen is two, and I’m wondering if it’s bad practice to have more than that.
You can have as many CCTimer or scheduled selectors
[self schedule:@selector(callMe:)]running as you want.Ultimately performance and/or memory usage depend a whole lot more on the code that is performed in a scheduled selector, rather than scheduling itself.
But it’s true, most classes in a Cocos2D project get along fine with just one scheduled update method. That’s why most of them simply use:
[self scheduleUpdate];