Re: Saving window and view state with NSDocument

> On Sep 21, 2015, at 12:09 PM, Kurt Sutter wrote: > > I am trying to figure out how to store information about my windows and views > in a document, and how to restore it. Here is what I do in one application. Override -[NSDocument

Re: Two Array Controllers, loading from CoreData, without a contentArray...

> Array Controllers etc. can be configured to monitor their context for changes and automatically re-fetch when needed. So they should keep in sync that way without any extra work. > It can? How? I'm only aware of the prepares content flag, but that'll only load the data into the controller when

OpenGL Vertical Syncing effect on run loops

In Apple document QA1385, in Listing 2, describing how to drive OpenGL Rendering Loops 10 years ago, an NSTimer, repeating every 1 millisecond, is added to an app’s run loop [1]. Referring to this timer, the text says that: "When vertical synchronization is enabled in your OpenGL application,

Re: Two Array Controllers, loading from CoreData, without a contentArray...

> On Sep 22, 2015, at 4:51 PM, Jim Thomason wrote: > > My request was specifically about keeping two NSArrayControllers in sync that > are -not- bound to a content array. Connect the first array controller to the managed object context. Bind the second array controller

Re: OpenGL Vertical Syncing effect on run loops

> On Sep 22, 2015, at 6:56 PM, Jerry Krinock wrote: > > In Apple document QA1385, in Listing 2, describing how to drive OpenGL > Rendering Loops 10 years ago, an NSTimer, repeating every 1 millisecond, is > added to an app’s run loop [1]. Just to be clear: don't do that.

Re: Two Array Controllers, loading from CoreData, without a contentArray...

> On Sep 22, 2015, at 7:40 AM, Jim Thomason wrote: > > The question is simple - is there a reasonable way to create two > NSArrayControllers, have them bound to an entity through CoreData, and keep > them in sync? One way would be to bind the two array controllers to the

Re: Two Array Controllers, loading from CoreData, without a contentArray...

My request was specifically about keeping two NSArrayControllers in sync that are -not- bound to a content array. The case I was tooling around with was for a root level object that just fetches all of its data automatically and bypasses any contentArray binding. Hypothetically, you could have

Re: Two Array Controllers, loading from CoreData, without a contentArray...

> On 22 Sep 2015, at 14:40, Jim Thomason wrote: > > First, to be clear, I'm not actually trying to do this. I'm just curious > how it could be done. I cooked it up while working on other things. > > The question is simple - is there a reasonable way to create two >

Re: Saving window and view state with NSDocument

Great study resource is TextEdit implementation (bit old but gives an idea). Try to select text - kill TextEdit.app - reopen TextEdit and see that it preserves selection. In documentation it's written that restoration is mainly used when your app is force closed due to restart. So do no expect it

Re: Saving window and view state with NSDocument

> On 22 Sep 2015, at 04:33, Kurt Sutter wrote: > > Thanks for the info > >> BTW you decided to fight against framework (as others mentioned state >> restoration is responsible for this). > > The documentation on state restoration is somewhat sparse. However, as I >

Two Array Controllers, loading from CoreData, without a contentArray...

First, to be clear, I'm not actually trying to do this. I'm just curious how it could be done. I cooked it up while working on other things. The question is simple - is there a reasonable way to create two NSArrayControllers, have them bound to an entity through CoreData, and keep them in sync?

Re: Saving window and view state with NSDocument

This is somewhat true. I've just tested it with "NSQuitAlwaysKeepsWindows" and the restore delegate is kicked when you quit app/launch app from the dock. However, it's not called when you perform close on window (hit the red cross). On Tue, Sep 22, 2015 at 10:56 AM, Mike Abdullah

About App size after using app thinning.

Hi all, I build my app with BitCode enable, and I encounter the same problem as below thread mentioned: https://forums.developer.apple.com/message/33429#33429 That is I archive my app and then export it to some variant, and I can see the size is around 155k ~ 165k compressed and 287k ~ 301k

Re: Saving window and view state with NSDocument

> On 22 Sep 2015, at 10:50, Marek Hrušovský wrote: > > This is somewhat true. > I've just tested it with "NSQuitAlwaysKeepsWindows" and the restore delegate > is kicked when you quit app/launch app from the dock. However, it's not > called when you perform close on window

Localised alert/confirm message

I use NSAlert to display a dialog with OK/Cancel, and noticed this had (wrongly) not been localized in my code. However, I noticed some other things. From the spec, if I replace OK/Cancel with other text, the automatic assignment of keyboard shortcuts is not done. All of this can be fixed, but I'm

Re: iOS 9 or Watch App

> On Sep 21, 2015, at 3:58 PM, Quincey Morris > wrote: > > Have you checked to make sure you don’t have a copy of Xcode 6 on an external > disk? Note that you can right-click on an existing project, and the Finder > will pop up a menu that shows you all