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.
I can't use the kCIContextWorkingColorSpace constant in CIContext, required to use CIContext.FromContext(EAGLContext, nsdictionary options), because it is named _WorkingColorSpace and is internal. There is a WorkingColorSpace property, but for ios9+ only, and its type is CGColorSpace not string.
Fixed in maccore/master 8f37569e95ab03d38f477576a7b22e87e0055737
A new overload will allow the use of `CIContextOptions` to provide the options.
> public static CIContext FromContext (EAGLContext eaglContext, CIContextOptions options)
This is an easier way to set the properties than a NSDictionary - but was missing for `EAGLContext`.
The workaround is to get load the NSString manually doing:
var ci = Dlfcn.dlopen ("/System/Library/Frameworks/CoreImage.framework/CoreImage", 0);
var constant = Dlfcn.GetStringConstant (ci, "kCIContextWorkingColorSpace");
I have checked it with latest C7 assembly and observed that CIContext FromContext (EAGLContext eaglContext, CIContextOptions options) is now public earlier it was internal.
Latest assembly having following code as mentioned in comment(1)
public static CIContext FromContext (EAGLContext eaglContext, CIContextOptions options)
XS Version 6.0 (build 5165)
Hence, Closing this issue