Re: Spinning the busy indicator
Re: Spinning the busy indicator
- Subject: Re: Spinning the busy indicator
- From: Graham Cox <email@hidden>
- Date: Fri, 01 May 2015 15:08:33 +1000
> On 1 May 2015, at 3:02 pm, Steve Mills <email@hidden> wrote:
>
> I’ve run into this too, where letting the OS figure out how many operations to queue at once doesn’t always work like a human wants it to work. I ended up doing what you did - leave one for the main thread. NSOperationQueueDefaultMaxConcurrentOperationCount really isn’t smart enough, or they need to add another constant NSOperationQueueDefaultMaxConcurrentButDontBeAJerkOperationCount.
>
Well, it’s always gratifying to find I’m not alone ;)
How did you figure out a value that leaves one for the main thread? The actual value returned is -1 for NSOperationQueueDefaultMaxConcurrentOperationCount, not the actual number it calculated. I guess there’s a way to get the number of cores, but that isn’t necessarily the whole story…?
—Graham
_______________________________________________
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