[icrate] Missing CoreGraphics and functions required for HDR/EDR

[mbrla0]

Is there any reason why icrate is missing support for CoreGraphics? Additionally, I find it weird that this crate is also missing both the setColorSpace and setWantsExtendedDynamicRangeContent functions. These are needed to properly make use of one of the HDR modes (Extended Dynamic Range) supported by Metal, as explained in this example.

(Edit: The functions are for properties in both CAMetalLayer and MTKView, my bad :))

[silvanshade]

Is there any reason why icrate is missing support for CoreGraphics?

I crate doesn't have bindings for several of the Core* frameworks at this point, not just CoreGraphics.

The main reason why is because the custom header-translator program that icrate uses to scan the frameworks and generate the Rust FFI declarations doesn't have great support for some of the lower-level more C-oriented functionality that the Core* frameworks require versus the more Objective-C oriented ones.

And although the header-translator generally works reasonably well, there are often times where certain methods have to be skipped during generation due to the header-translator not being able to correctly parse the corresponding code in the header, or support lacking for some part of the definition on the Rust side.

This is the case for setColorSpace. And setWantsExtendedDynamicRangeContent isn't available because CAMetalLayer isn't supported by icrate yet (for the above reasons).

It's often still possible to work around these missing functions by using msg_send_id! to call the selector directly, although this is obviously less safe, so more care needs to be taken to ensure the types are correct.

[madsmtm]

CAMetalLayer is available since 05f6787, and in 888ba81 I added a bit of documentation for how to interoperate with core-graphics.

Adding CoreGraphics proper is tracked in #556, so going to close this.