Glad that worked. I'll also file some docs bugs. Another way to do this is to implement a controller or container that handles it.
View controllers are in the responder chain and can act as the item that needs validation and set the control properties. We can also look at the design of toolbar items and menu items as containers for views, so they can do a similar job. These approaches might let you avoid some control subclassing (depending on what else you need to do) and might let you stay in swift. Sent from my iPhone > On Dec 15, 2015, at 6:56 AM, Luc Van Bogaert <luc.van.boga...@me.com> wrote: > > >>> On 14 Dec 2015, at 22:51, Roland King <r...@rols.org> wrote: >>> >>> >>>> On 15 Dec 2015, at 04:10, Luc Van Bogaert <luc.van.boga...@me.com> wrote: >>> >>> >>> I tried what you suggested and made a button subclass and just declared >>> conformance in objective-c, and then imported the class into Swift. >>> This seems to do the trick, my button subclass is now accepted as >>> conforming to the protocol. >>> Thanks! >> >> Good - If you can find 5 minutes I really would suggest filing a bug report >> on it, it’s nice to be able to work around it for now but it’s something >> needs to get fixed, the protocol definition is inconsistent in Objective C >> (defined as properties, implemented as functions) and that needs cleaning up >> or special-casing. > > Done it already. > > -- > Luc Van Bogaert _______________________________________________ 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
