Home/ Questions/Q 7193773
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T20:14:16+00:00

This problem started happening when I subclassed CCSprite (Entity) to recieve touch input. When

  • 0

This problem started happening when I subclassed CCSprite (Entity) to recieve touch input. When I’m going away from the main scene by pushing to another, I make all Entities remove their delegation from the shared CCTouchDispatcher (ie onExit()). And then reactivate when the main scene returns (onEnterTransistionFinished()).

Half of the times this works fine. However, the other times this happens:

cocos2d: deallocing <CCScheduler: 0x2323a0>

Which I find rather strange. Is it even plausible that the Touch Delegates are the cause of the problem? Or is it perhaps memory-related?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If I remember correctly the problem originated from trying to register/unregister the same Entity to/from the TouchDispatcher twice (ie it didn’t have time to unregister/register before I tried registering/unregistering it again).

    I solved it by adding a little BOOL _didRegisterWithTouchDispatcher to avoid doing something like that.

    • 0