The bug should be that it gives you a wrong message, because it already conforms to the protocol because it inherits from a class that conforms to the protocol.
All you should have to do is implement an override of the methods to do custom stuff or of the properties. You shouldn't declare conformity to NSValidatedUserInterfaceItem because it already confirms earlier in its ancestry. Sent from my iPhone > On Dec 14, 2015, at 6:02 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > >> On Dec 13, 2015, at 23:53 , Roland King <r...@rols.org> wrote: >> >> You appear to be a little out of luck here because > > I was afraid that was going to be the answer. I suspect the problem is the > Swift Obj-C importer, rather than any misguided SDK intention, because there > are also a *lot* of accessibility properties that come across as functions. > Maybe I’ll file a bug report for that manifestation too. > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com > > This email sent to dangerwillrobinsondan...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
