Skip to content

Conversation

@1scaR1
Copy link
Contributor

@1scaR1 1scaR1 commented Mar 7, 2017

It seems to be ok to enable retina support.
I don't why it was disabled at all...

@pandamicro
Copy link
Contributor

Actually this macro is never used and never set, cc.view.isRetinaEnabled() is the correct API, we haven't cleanup these macros

@1scaR1
Copy link
Contributor Author

1scaR1 commented Mar 8, 2017

It's actial use in cc.contentScaleFactor function. If this macro is set to 0 then this functions always returns 1.
In actual code it breaks compability with jsb on retina displays, because 'setContentScaleFactor' not works.
If you want to remove this macro my propose is to set cc.contentScaleFactor always to return Director's _contentScaleFactor in this PR. Is it right?

@pandamicro
Copy link
Contributor

If you want to remove this macro my propose is to set cc.contentScaleFactor always to return Director's _contentScaleFactor in this PR. Is it right?

I think it would be more proper

@1scaR1
Copy link
Contributor Author

1scaR1 commented Mar 8, 2017

@pandamicro Done! Please, review

@pandamicro pandamicro merged commit fa8edd4 into cocos2d:develop Mar 8, 2017
@pandamicro
Copy link
Contributor

Thanks~

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