/jporter
hardcore_programmer
def
showpage
__
Aaaand that’s probably horribly mangled postscript; but you’ll have to forgive
me, as I haven’t had to read it in years, and have never had to write it in
earnest…
But to
In my OS X single-window application (not document-based), written using
storyboards in Swift 2, I implement the NSWindowRestoration protocol's static
function restoreWindowWithIdentifier(_:state:completionHandler). I have reached
the point where it is called when it is supposed to be called.
B
On Mar 3, 2016, at 05:27 , Bill Cheeseman wrote:
>
> I use MainWindowController as the restoration class:
>
>static func restoreWindowWithIdentifier(identifier: String, state:
> NSCoder, completionHandler: (NSWindow?, NSError?) -> Void) {
>let controller = MainWindowController()
>
> On Mar 3, 2016, at 1:32 PM, Quincey Morris
> wrote:
>
> — There’s nothing wrong with using MainWindowController as your restoration
> class (AFAIK), because the restoration method is a static func.
>
> OTOH, there’s no particular reason, in *this* part of the restoration
> mechanism, to ti
This new Xcode project (with storyboards) makes new windows at the same
coordinates, on top of each other. Just the ever increasing shadow gives that
behavior away. Is there a way to (automatically) get that old Mac behavior of
staggered windows? I think it was 20 pixels down and right.
Sent fr
> On Mar 3, 2016, at 2:46 PM, Daryle Walker wrote:
>
> This new Xcode project (with storyboards) makes new windows at the same
> coordinates, on top of each other. Just the ever increasing shadow gives that
> behavior away. Is there a way to (automatically) get that old Mac behavior of
> stagg
On 3/3/16 12:00 PM, Britt Durbrow wrote:
Britt; thanks for the quick reply.
I deleted everything from the folder that I did not create, then
stripped them from the project. This allowed the 10.5 version to find
the right plist.
I then did a copy on the build target, which I renamed, then cha
