Skip to content
This repository was archived by the owner on Feb 2, 2023. It is now read-only.

Conversation

@samhsiung
Copy link
Contributor

Future plans could be to add child nodes to UIVisualEffectView's contentView and not it's subview which Apple recommends:
After you add the visual effect view to the view hierarchy, add any subviews to the contentView property of the visual effect view. Do not add subviews directly to the visual effect view itself.
https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIVisualEffectView/

Copy link
Contributor

Choose a reason for hiding this comment

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

You'll want to include this header in AsyncDisplayKit.h so that it can be used outside of the framework. Also, update the copyright preamble to reflect the one used in the other classes.

@appleguy
Copy link
Contributor

Cool idea! We may want to install some checks or robustness around this to make sure that people aren't confused if they try to do shouldRasterizeDescendents and find that the effect is missing. Might be able to throw an assertion if rasterization encounters one of these nodes...

@samhsiung
Copy link
Contributor Author

Going to test contentView children functionality some more

@samhsiung samhsiung closed this Nov 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants