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.
None of the SCNAction methods used to create actions are bound:
They are actually bound in another class called SCNActions (Apple hangs them all off SCNAction).
I see, we created them in SCNActions as extension methods.
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.
Mac OS X 10.9.3
Xamarin Studio:5.0.1 (build 3)
Xamarin.iOS: 188.8.131.528 (Enterprise Edition)
Release ID: 500010003
Git revision: f94ee866936d25105704eb63728ad5a981eda0a4
Build date: 2014-06-04 12:19:12-04
Xamarin addins: 1a6044e8321ea07e03a56b5381951686c82fed8b
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).
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
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.