Re: Spinning the busy indicator
Re: Spinning the busy indicator
- Subject: Re: Spinning the busy indicator
- From: Fritz Anderson <email@hidden>
- Date: Fri, 01 May 2015 12:59:23 -0500
On 1 May 2015, at 12:53 AM, Graham Cox <email@hidden> wrote:
>
> So, the docs say (ha! here we go again…) that the default QoS is NSOperationQualityOfServiceBackground. This appears to be the LOWEST QoS constant. However, it also states that it is only used if the NSOperation itself doesn’t set this value, but because addOperationWithBlock: creates its own NSOperation internally (that we mere mortals don’t get to access), it might be assigning a value that overrides this. Unhelpfully, the simple CPU usage view in XCode only states "QoS unavailable”.
>
> It looks as if to be sure I’m going to have to drop down a level and create my own NSOperations.
Idle curiosity — if your operations queue is all your own, is there a point in your process in which you can iterate its .operations array and set QoS then? There’s no explicit promise that the property is mutable after the operation is enqueued, though, and you might be Too Late already.
This may be moot. You have a workaround, and Kyle accepts that it may be a bug.
— F
_______________________________________________
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