> On 2 May 2015, at 2:42 am, Kyle Sluder wrote:
>
>> Well that’s an interesting result - creating my own NSOperation with a
>> QoS of NSOperationQualityOfServiceBackground and adding it to my queue
>> produces a perfectly smooth and non-blocking app. If I use
>> -addOperationWithBlock: things ar
On May 1, 2015, at 14:02:27, Sean McBride wrote:
> In my NSPersistentDocument subclass I created a new initializer, which
> stripped of error checking, is basically:
>
> - (instancetype)initWithTemplate
> {
> self = [super init];
>
> [self readFromURL:
>
On Fri, 1 May 2015 13:36:49 -0500, Steve Mills said:
>Can’t you just set the document’s url to nil at some point? That’s what
>I do in readFromURL:ofType:error: after reading the file (actually
>before reading, because I don’t access the url again from the document).
>I’m using regular NSDocument,
> On May 1, 2015, at 08:58 , Fritz Anderson wrote:
>
> I almost devoted half-a-chapter to how disastrous and inexplicable this is,
> until I figured out the rules. Part of the rant made it through to the page
> proofs (print minus one).
>
> Storyboards are not monoliths at runtime, they’re an
On May 1, 2015, at 13:26:26, Sean McBride wrote:
>
> Hi all,
>
> I have an NSPersistentDocument-based application.
>
> I'd like to be able to create new/untitled/unsaved documents that are
> pre-populated with various managed objects. Instead of creating the objects
> programatically, I'd li
Hi all,
I have an NSPersistentDocument-based application.
I'd like to be able to create new/untitled/unsaved documents that are
pre-populated with various managed objects. Instead of creating the objects
programatically, I'd like to load them from a template document (hidden inside
my .app).
On 1 May 2015, at 12:53 AM, Graham Cox 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 va
On Fri, May 1, 2015, at 01:41 AM, Graham Cox wrote:
>
> > On 1 May 2015, at 3:53 pm, Graham Cox wrote:
> >
> > It looks as if to be sure I’m going to have to drop down a level and create
> > my own NSOperations.
>
> Well that’s an interesting result - creating my own NSOperation with a
> QoS o
On 28 Apr 2015, at 6:54 PM, Rick Mann wrote:
> I have a window made up of a couple of NSSplitViewControllers and custom view
> controllers. It's mostly a master-detail type of thing, where the selected
> item in the first split sets up the second, and a selected item there sets up
> the third
> On 1 May 2015, at 19:13, Uli Kusterer wrote:
>
> On 01 May 2015, at 04:15, Graham Cox wrote:
>> When the calculation for a tile is finished, it calls its delegate to tell
>> it it has finished. The delegate is the original view. I use
>> -performSelectorOnMainThread: to notify the delegate.
On 01 May 2015, at 06:46, Graham Cox wrote:
> I use NSOperationQueue with the default -maxConcurrentOperationCount which is
> NSOperationQueueDefaultMaxConcurrentOperationCount, i.e. let the system
> figure it out. That appears to create 4 threads for my particular machine,
> which has a Core i
On 01 May 2015, at 04:15, Graham Cox wrote:
> When the calculation for a tile is finished, it calls its delegate to tell it
> it has finished. The delegate is the original view. I use
> -performSelectorOnMainThread: to notify the delegate.
Idea: Have you tried using
performSelectorOnMainThread
On Apr 30, 2015, at 23:41 , Graham Cox wrote:
>
> I’d be interested to know if this has changed from 10.9 or earlier (I’m on
> 10.10).
Oh, QoS is 10.10+ only. Before that there was threadPriority and queuePriority
for NSOperation, and the old GCD dispatch queue priorities correspond to the
ne
13 matches
Mail list logo
