Bug 20825 - SCNAction methods to create actions are not bound
Summary: SCNAction methods to create actions are not bound
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 7.9.0.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-06-23 16:46 UTC by Mike Bluestein
Modified: 2014-06-24 17:34 UTC (History)
5 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 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:
Status:
RESOLVED FIXED

Description Mike Bluestein 2014-06-23 16:46:10 UTC
None of the SCNAction methods used to create actions are bound:

https://developer.apple.com/library/prerelease/ios/documentation/SceneKit/Reference/SCNAction_Class/index.html#//apple_ref/occ/cl/SCNAction
Comment 1 Mike Bluestein 2014-06-23 16:48:13 UTC
They are actually bound in another class called SCNActions (Apple hangs them all off SCNAction).
Comment 2 Mike Bluestein 2014-06-23 16:52:23 UTC
I see, we created them in SCNActions as extension methods.
Comment 3 Sadik Ali 2014-06-24 09:16:56 UTC
I have checked this issue and I am getting the same behavior.

Steps to reproduce:

1. Open an iOS "Single View Application" in XS.
2. Open "Assembly Browser" (View=>Assembly browser")
3. Search "SCNAction" class in "Assembly browser".
4.  Methods of "SCNAction" class are bounded to "SCNActions"

I observed that in apple doc the methods of "SCNAction" are bounded in the same class but in Xamarin these methods are bounded to the "SCNActions" class which is created as a extension methods.

When I check the definition of "SCNAction" class I observed that the only few method/property are bounded to the "SCNAction" class  for example ("ReversedAction") and all other method are bounded to the "SCNActions" class which is created as extension methods.

Screencast: http://www.screencast.com/t/or2b3XLCt

Environment Info:

Mac OS X 10.9.3
Xamarin Studio:5.0.1 (build 3)
Xamarin.iOS: 7.9.0.278 (Enterprise Edition)

Build Information

Release ID: 500010003
Git revision: f94ee866936d25105704eb63728ad5a981eda0a4
Build date: 2014-06-04 12:19:12-04
Xamarin addins: 1a6044e8321ea07e03a56b5381951686c82fed8b
Comment 4 Sebastien Pouliot 2014-06-24 10:26:24 UTC
I think (c.c. Aaron) that it's an artefact of objsharpie, i.e. not a conscious decision.

IOW Apple defines them in a separate type (category), see SCNAction.h header file

    @interface SCNAction (SCNActions)


and that got mapped into a separate .NET type (and categories become extensions methods).
Comment 5 Miguel de Icaza [MSFT] 2014-06-24 15:09:26 UTC
Agreed, the names of those categories are typically arbitrary, and we default to merging those into the class itself, unless they only bring features that are surfaced on a different framework or when their meaning would be ideal on its own.

This not being the case, I am making the change
Comment 6 Aaron Bockover [MSFT] 2014-06-24 17:34:17 UTC
It's an "artifact" in that yes, Objective Sharpie generates a category when it encounters one.

I wasn't sure what our category convention was when I audited the binding, so I left it as is - seeing that it generated extension methods.