I am getting an unrecognized selector error when I call any of the static members of the IGColumnWidth class. I wrote my own bindings previously that were working, but I decided to try the beta bindings to see if they worked.
Here is the exception details:
2012-10-17 11:07:54.504 HPSISalesTool[1766:1507] +[IGColumnWidth CreateWithFixedWidth:]: unrecognized selector sent to class 0x4421a42012-10-17 11:07:54.512 HPSISalesTool[1766:1507] MonoTouch.Foundation.MonoTouchException: Objective-C exception thrown. Name: NSInvalidArgumentException Reason: +[IGColumnWidth CreateWithFixedWidth:]: unrecognized selector sent to class 0x4421a4 at (wrapper managed-to-native) MonoTouch.ObjCRuntime.Messaging:IntPtr_objc_msgSend_float (intptr,intptr,single) at Infragistics.IGColumnWidth.CreateWithFixedWidth (Single width) [0x00000] in <filename unknown>:0 at HPSISalesTool.UI.Members.MemberDetailsView+CheckHistoryGridViewDelegate.GridViewWidthForColumnAtIndex (Infragistics.IGGridView gridView, Int32 column) [0x0001d]
Is there a reason that constructor bindings weren't created for this type? That is what I did and it worked well.
Thanks for the report, that definitely is an issue.
The reason we couldn't use a constructor for the IGColumnWidth, is that there are actually 4 constructors. And 2 of them actually have the same parameters. Thats not an issue in objective-c b/c they can have different names. However, in monoTouch the bindings have to be Constructor, so they'd have the same name, which isn't allowed.
Again thanks for the report!
Thanks for the quick response, I will just go back to my bindings until a fix is released. In regards to the constructor, I went back and looked at my binding and I realized that I used an NSObject for one of the parameters to avoid the type collision. Works on a smaller project, but probably not best for a library so it makes sense to do it the way you guys did.
Is there any possibility that you could share the .cs files for the MonoTouch bindings?
I believe that you have been already communicated this with Steve and everything should be fine now.
Thank you for choosing Infragistics.