On May 02, 2016, at 02:19 PM, Alex Zavatone <z...@mac.com> wrote:
What was the compelling reason for you guys to use this functionality on purpose, ease of data access? It seems like it might leave many loose ends and I'm looking for ways to reduce the amount of rope we use to hang ourselves. What was the benefit it offered your team? It's been a long time since I had that job, so it's a little fuzzy. I recall it being very helpful for classes that we couldn't subclass for some reason or other. I see one mention of it being used on each NSCell of some buttons in tool palettes. The category method we added was objectUserInfo, which would attempt to get the associated object. If it was nil, it would create a mutable dict and set the associated object, and return the dict. That way, every object could have a dict "property" that could be used however the client wanted. Sent from iCloud's ridiculous UI, so, sorry about the formatting
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
