Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added public property to allow a CCSprite subclass to forcefully disable debug drawing. #234

Closed
wants to merge 4 commits into from
Closed

Added public property to allow a CCSprite subclass to forcefully disable debug drawing. #234

wants to merge 4 commits into from

Conversation

Panajev
Copy link
Contributor

@Panajev Panajev commented Sep 11, 2012

When using Cocos2D as an external static library, the macro used to influence certain Cocos2D features, such as Debug drawing for CCSprites, are fixed when the library is compiled.

A workaround might be to compile the library in Release and Debug versions with the DEBUG flag directing, for example, when the debug drawing macro's allow the debug shapes to be rendered.
The problem is that this might cause cases in which the debug drawing feature for CCSprite objects is not really usable: if you have a few sprites moving in front of a large background (with the background being essentially just a large CCSprite object in some instancea), all the user will see is a huge white shape and will not be able to discern the small sprites in the foreground.

If we allow the CCSprite to override the debug drawing macro at runtime, we do not either lose performance in release mode and we make debug mode more flexible preventing the case mentioned above.

It only supports transitions responding to this message:

+(id) transitionWithDuration:(ccTime) t scene:(CCScene*)s
…rientation related transition methods to bring them more in line with the colour based fading methods.

Added new CCTransitionOrientationType.h header to allow this enum to be
used in the Director without importing the whole CCTransition.h header.
@Panajev
Copy link
Contributor Author

Panajev commented Sep 11, 2012

Uhm, sorry... the other three commits are related to the support for pushing and popping scenes with transitions which I already included in a separate pull request, should I cancel that pull-request?

@Birkemose Birkemose closed this Mar 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants