Issues with CIFilters and CALayers
Issues with CIFilters and CALayers
- Subject: Issues with CIFilters and CALayers
- From: Gordon Apple <email@hidden>
- Date: Sun, 23 Feb 2014 15:06:13 -0600
- Thread-topic: Issues with CIFilters and CALayers
We have run into a number is issues trying to use CIFilters with CALayers:
1. When a layer is hidden, its filters, especially background filters,
should be temporarily removed, or at least bypassed. Hiding the layer
should make if effectively non-existent in the displayed layer stack.
2. The docs should tell you that in a CIFilter you cannot auto-synthesize
filter input parameters. This simply does not work, especially for
inputImage.
3. The docs for CALayer filters and background filters say you should name
your filters for use in changing parameters. I.e., filter.name =
@²myFilter². Amazingly, this works, in spite of the fact that there is no
public property called ³name² for a CIFilter.
4. The example keyPath makes no sense whatsoever, unless we just don¹t
understand keyPaths:
[layer setValue:XXX forKeyPath:@²backgroundFilters.myFilter.filterParam²];
backgroundFilters is an array of filters. myFilter is a property value of
some element of the array. (huh?)
5. We need some decent documentation of what in GL Shading Language is
actually relevant to writing ciKernels, besides the one page addendum
provided.
6. And, of course, the problem we have already mentioned in a previous post
about getting a CALayer to update when a filter parameter is changed.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden