Skip to content

problem with canvas2d #3275

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

janKristek
Copy link

Problem with canvas2d, when FileNode have other inner fileNode and inner fileNode have loop animation and main fileNode have animation change color. If play animation which change color without loop, inner FileNode have problem with no rotated image in atlas only in Canvas2d in webGL works normal (example with cocos2d-html5 v.11:http://mab.to/eo7YoVAs9)

…ner fileNode have loop animation and main fileNode have animation change color.If play animation which change color without loop, inner FileNode have problem with no rotated image in atlas only in Canvas2d in webgl works normal (example with cocos2d-html5 v.11:http://mab.to/eo7YoVAs9)
@@ -201,8 +201,10 @@
textureLoaded = textureLoaded || pNewTexture._textureLoaded;
if (textureLoaded) {
var curColor = this._node.getColor();
if (curColor.r !== 255 || curColor.g !== 255 || curColor.b !== 255)
if (curColor.r !== 255 || curColor.g !== 255 || curColor.b !== 255||
this._displayedColor.r !== 255 || this._displayedColor.g !== 255 || this._displayedColor.b !== 255) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should only check displayedColor, we can assume it's always synced or generated with node's color.

@pandamicro
Copy link
Contributor

Thanks for the contribution, can you remove the check for node's color so that I can merge it

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