Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
CIContext currently has a FromContext method to create from an EAGLContext and a FromOptions method to create from a CIContextOptions object, but no constructor or method that accepts both an EAGLContext and a CIContextOptions object, to match the objective-c method [CIContext contextWithEAGLContext:options:]
Fixed in master 4775c394297635b10a32b2f5e1656d1266a1e3f0
I have checked this issue on following builds:
Mac OS X 10.7.5
Xamarin Studio: 4.2.3 (build 60)
Xamarin.iOS: 220.127.116.11 (Trial Edition)
Release ID: 402030060
Git revision: 30c4afc300c2a39ec5300851357ce02e49dd217e
Build date: 2014-03-05 22:09:33+0000
Xamarin addins: f8a9589b57c2bfab2ccd73c880e7ad81e3ecf044
I have checked the declaration of "CIContext" class in "assembly browser" and I observed that now we have
a static method which takes two parameter one is of type "EAGLContext" and another one is "NSDictionary "
type, which is same as "apple documentation" for "CIContext" class (https://developer.apple.com/library/ios/documentation/graphicsimaging/reference/QuartzCoreFramework/Classes/CIContext_Class/Reference/Reference.html#//apple_ref/occ/clm/CIContext/contextWithEAGLContext:options:) .
This issue is working fine. Hence, I am closing this issue.