Bug 59433 - Coerce AVDepthData.AvailableDepthDataTypes to return MonoTouch.CoreVideo.CVPixelFormatType?
Summary: Coerce AVDepthData.AvailableDepthDataTypes to return MonoTouch.CoreVideo.CVPi...
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.99 (xcode9)
Hardware: PC Mac OS
: --- normal
Target Milestone: Xcode9
Assignee: Alex Soto [MSFT]
Depends on:
Reported: 2017-09-12 20:37 UTC by Mike Norman
Modified: 2017-09-13 15:05 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 Mike Norman 2017-09-12 20:37:09 UTC
Hey, we have `AVDepthData.AvailableDepthDataTypes` bound to return an array of NSNumbers. However, the Apple help says it's suitable for use with `depthDataByConvertingToDepthDataType`, which we have bound to a `Create` overload that takes `MonoTouch.CoreVideo.CVPixelFormatType`. Should we be coercing `AvailableDepthDataTypes` to return an array of `CVPixelFormatType`s, instead?
Comment 1 Alex Soto [MSFT] 2017-09-13 02:03:20 UTC
Yes, this makes sense to have, nice find!
Comment 2 Alex Soto [MSFT] 2017-09-13 08:36:18 UTC
PR: https://github.com/xamarin/xamarin-macios/pull/2676

Your suggestion turned out to be quite useful, thanks Mike!
Comment 3 Alex Soto [MSFT] 2017-09-13 15:05:08 UTC
Fixed in xamarin-macios/xcode9 at 97f46ea685e60f63417c7f4f66d750560e402a56