> On Aug 10, 2016, at 1:35 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On Aug 10, 2016, at 13:29 , Doug Hill <cocoa...@breaqz.com > <mailto:cocoa...@breaqz.com>> wrote: >> >> Again, looking for any ideas, pointers, etc. about any of this, including >> whether I'm going about this the wrong way. > > This is something that you should use a TSI for. Because collection views > have evolved over OS generations, it’s now hard to separate documentation > errors from compatibility modes from recommended design and coding practices > of various eras. Even if you don’t have a free TSI available, paying for one > is likely the best strategy, and the best use of your time.
Quincy, Thanks for the feedback. I was definitely considering this but I thought I'd throw this out to the developer community first so I can at least know I'm not missing something obvious. Also, Apple support folk seem to get testy when you ask what is considered a "dumb" question. Finally TSI cost money and I don't want to waste this valuable resource on something I can find out from the community. Although, this basically means that Apple's documentation is a fail and the APIs don't work in a predictable way. Again, this should also be noted so other developers don't go through all the trouble I've done to implement very basic functionality. Or maybe *hint hint* Apple could update this documentation and/or fix these bugs. Doug Hill _______________________________________________ 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
