• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa-dev Digest, Vol 14, Issue 154
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa-dev Digest, Vol 14, Issue 154


  • Subject: Re: Cocoa-dev Digest, Vol 14, Issue 154
  • From: Steve Mills <email@hidden>
  • Date: Tue, 02 May 2017 14:45:55 -0500

On May 2, 2017, at 14:40:59, J. Scott Tury <email@hidden> wrote:
>
> In short, use Instruments to see what your app is really processing for your collectionView.  You may be surprised at what is happening.  Once those interactions are cleaned up, performance should be good.

Thanks, but performance isn't the issue. The feature set and implementation is the issue. I only mentioned performance because of course I want a substitute to have equal or better performance than NSCollectionView.

--
Steve Mills
Drummer, Mac geek

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Re: Cocoa-dev Digest, Vol 14, Issue 154 (From: "J. Scott Tury" <email@hidden>)

  • Prev by Date: Re: Cocoa-dev Digest, Vol 14, Issue 154
  • Next by Date: Creating NSStrings without copying memory
  • Previous by thread: Re: Cocoa-dev Digest, Vol 14, Issue 154
  • Next by thread: Creating NSStrings without copying memory
  • Index(es):
    • Date
    • Thread