I found somewhat interesting behavior.
When it doesn't use property to set an instance of CALayer like this :
m_imageLayer = [CALayer layer];
instead of
self.imageLayer = [CALayer layer];
it doesn't cause the problem anymore.
Instead of using property, I tried to use a setter and a getter methods for
being sure like :
- (void)setImageLayer:(CALayer *)layer;
- (CALayer *)imageLayer;
[self setImageLayer:[CALayer layer]];
Then it presented the same problem.
So, somehow CALayer looks to be assigned directly instead of using properties.
Once assigned directly, it doesn't matter whether to set filter by
[self.imageLayer setFilter:...] or
[m_imageLayer setFilter...]
Is there any reason why it works like that?
Thank you.
JongAm Park
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
