On Fri, Mar 30, 2012 at 10:31 PM, Peter Teeson <ptee...@me.com> wrote: > Rather than using a sub-class, which seems overkill to me, > I decided to try a Category instead. So here's what I did (and it seems to > work.)
The problem with this approach is that you've replaced the drawRect: for every NSMatrix instance, everywhere, in your app. If some Cocoa control is using NSMatrix, suddenly it's using your drawRect:. If you decide to use NSMatrix somewhere else, it too is using this drawRect:. I wouldn't trust this to be very stable. And I don't see how subclassing is much more work than this. _______________________________________________ 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
