Hi,
According to the API documentation, the activeKeys property of the CIRAWFilterOption struct is deprecated. What is its replacement functionality?
Cheers.
Michael
I think the whole RAW development is now handled by the new CIRAWFilter.
This doesn't have an activeKeys property anymore. Instead, you can check for each property individually if it's supported or not. For instance with isContrastSupported or isMoireReductionSupported.
Thank you, Frank! I didn't notice those properties before. I'm accepting your answer as the correct one.
Though this opinion has no bearing on the correctness of your answer, I think that deprecating the RAW filter's introspective key-value API in favor of a "static", property-based API is a mistake. I see a place for both kinds of APIs, where each complements the other. If you believe there's still a non-deprecated API that would allow developers to read and write RAW filter input keys at runtime, I would love to hear. I hope the deprecated API remains indefinitely supported in the future, even if Apple discourages its use.
I think the whole RAW development is now handled by the new CIRAWFilter.
This doesn't have an activeKeys property anymore. Instead, you can check for each property individually if it's supported or not. For instance with isContrastSupported or isMoireReductionSupported.
Thank you, Frank! I didn't notice those properties before. I'm accepting your answer as the correct one.
Though this opinion has no bearing on the correctness of your answer, I think that deprecating the RAW filter's introspective key-value API in favor of a "static", property-based API is a mistake. I see a place for both kinds of APIs, where each complements the other. If you believe there's still a non-deprecated API that would allow developers to read and write RAW filter input keys at runtime, I would love to hear. I hope the deprecated API remains indefinitely supported in the future, even if Apple discourages its use.
