Bug 45528 - SCNRenderingOptions.RenderingApi binding uses incorrect key
Summary: SCNRenderingOptions.RenderingApi binding uses incorrect key
Status: CONFIRMED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-10-16 02:45 UTC by Frank A. Krueger
Modified: 2016-11-29 16:58 UTC (History)
3 users (show)

Tags:
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 for Bug 45528 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Frank A. Krueger 2016-10-16 02:45:27 UTC
SCNRenderingOptions.RenderingApi queries SCNRenderingOptionsKeys.RenderingApiKey from itself to determine the key.

This makes no sense.

It should simply SetNumberValue using the RenderingApiKey.
Comment 1 Frank A. Krueger 2016-11-29 16:58:01 UTC
This bug has been confirmed for over a month but is still not assigned to anyone or a milestone.