Bug 9477 - CoreImage filters should include a strongly-typed OutputImage property
Summary: CoreImage filters should include a strongly-typed OutputImage property
Alias: None
Product: MonoMac
Classification: Desktop
Component: Bindings ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-01-10 20:22 UTC by Alex Corrado [MSFT]
Modified: 2015-02-13 17:59 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Alex Corrado [MSFT] 2013-01-10 20:22:04 UTC
It's not clear how to get the output image on CoreImage filters like CIPerspectiveTransform and CIColorControls. It turns out you need to do something like:

 (CIImage)filter [CIFilterOutputKey.Image]

However, we expose strongly-typed properties for a lot of the filter attributes, so it's not intuitive. On iOS we expose the OutputImage property because ObjC does. I think we should bring that to the Mac bindings as well.
Comment 1 Timothy Risi 2015-02-13 17:59:36 UTC
The strongly-typed OutputImage property has been added to the core image filters.