Why is the contentRect of my NSWindow ignored?

When creating an NSWindow, you can pass a contentRect to set its size and position. But for me, the size and position were being ignored. The culprit was a call to setFrameAutosaveName. Here I describe what setFrameAutosaveName does, since it has no documentation.

Create a new macOS app in Xcode, and it will give you some Swift like this:

var window = NSWindow(
    contentRect: NSRect(x: 0, y: 0, width: 480, height: 300),
    styleMask: [.titled, .closable, .miniaturizable, .resizable, .fullSizeContentView],
    backing: .buffered, defer: false)
window.center()
window.setFrameAutosaveName("Main Window")
window.contentView = NSHostingView(rootView: contentView)
window.makeKeyAndOrderFront(nil)
}

The window it gives you can be resized and repositioned with the mouse. But try playing around with the contentRect: NSRect(x: 0, y: 0, width: 480, height: 300), and you’ll find that the values are stubbornly ignored! There are a couple of reasons for this.

The first reason is the call to window.center(). This changes the position of the window to be centered on the display, so your earlier x and y values are effectively ignored. But removing window.center() still won’t fix the issue.

The second, more interesting reason is the call to window.setFrameAutosaveName("Main Window"). There are no docs for setFrameAutosaveName, but here’s what it does. When the user moves or resizes a window that has an autosave name, the size and position are saved to the user defaults under that autosave name. Then when a window is created with an autosave name, if a size and position have been saved to user defaults, these preferences override the contentRect passed in the constructor. Here you can see the defaults after I moved and resized my "Main Window" window:

$ defaults read baz.ContentRectTest
{
    "NSWindow Frame Main Window" = "565 282 680 600 0 0 1680 1027 ";
}

The format here seems to be:

"NSWindow Frame \(autosaveName)" = "\(window.frame.x) \(window.frame.y) \(window.frame.width) \(window.frame.height) \(screen.x) \(screen.y) \(screen.width) \(screen.height - menuBar) ";

I don’t know why it also saves the details of the screen.

WFH on lockdown, like me? Let’s help each other out! I just released Vidrio, a free app for macOS and Windows to make your screen-sharing awesomely holographic. “Oh damn that's genius”, said some YouTuber when he saw it. But don't believe him, or the #1 on Product Hunt. Instead, believe this demo:

With Vidrio

With generic competitor

More by Jim

Tagged #programming. All content copyright James Fisher 2020. This post is not associated with my employer. Found an error? Edit this page.