GLKit workaround #trivial#54
Conversation
canClearContentsOfLayer now turned off for views with CAEAGLLayer
nguyenhuy
left a comment
There was a problem hiding this comment.
Nits aside, LGTM although I'd prefer another approval from a core maintainer before merging.
|
|
||
| // CAEAGLLayer | ||
| if([view.layer.class isSubclassOfClass:[CAEAGLLayer class]]){ | ||
| _flags.canClearContentsOfLayer = NO; |
| } | ||
|
|
||
| // CAEAGLLayer | ||
| if([view.layer.class isSubclassOfClass:[CAEAGLLayer class]]){ |
There was a problem hiding this comment.
Nit: [view.layer class] for consistency.
|
Fxd |
maicki
left a comment
There was a problem hiding this comment.
We may should start now thinking about a better structure around specific classes that need special handling as there are quite a couple different cases now. But this looks good to me.
|
@maicki Agreed! |
|
@stephenkopylov Would you mind signing the CLA? |
|
@nguyenhuy |
|
@stephenkopylov Could you try to add the email to your account?
|
|
@nguyenhuy hooray! that was because I pushed PR from office, where I use different email. |
|
Sry guys, I missed one square bracket. Fxd |
Generated by 🚫 Danger |
| // | ||
| // ASDisplayNode.mm | ||
| // AsyncDisplayKit | ||
| // Texture |
|
@stephenkopylov Thanks for being patient and working through all of the hurdles. Hope to see more PRs from you! |

canClearContentsOfLayer now turned off for views with CAEAGLLayer
more:
#53