Glad that fixed it! When you create a new source file for a class that's derived from NSWindowController, Xcode will offer to make the class files as well as a XIB file (all wired up) for you.

Indeed it was not. After connecting it as it should have been, now all works perfectly as expected. Thanks a lot for this brilliant idea! This brings up another question: I seem to remember that once

Getting a little closer on this one. Apparently the UILabels within the UIActionViews have the appropriate text, but the UILabel and the UILabel’s tint colors are 0 or close to it and the font

Both have: app → Content → Resources → de.lproj → PrefWindow.strings

Is the 'window' outlet of the XIB file's owner set to point to the window in the XIB? It doesn't sound like it. - Jon

Did you check to see that the German localization of your strings is included in both targets? If you open both of the app bundles do you see de.lproj folder > PrefVWindow.strings in both?

if ( self.prefController == nil ) { self.prefController = [ [ NSWindowController alloc ] initWithWindowNibName: @"PrefWindow" ]; NSLog(@"%s prefController %@",__FUNCTION__,

This is — in some sense — impossible. There is a window. (You can see it.) Either the debugger is lying to you, or the window is unrelated to the window controller. Whichever it is, it’s worth

It never has. Even after the first time where showWindow will succeed. Kind regards, Gerriet.

I would suggest that you look in the debugger at whether the window controller *has* a window the second time around. (Note that the “window” property automatically loads the window if necessary,

I have two apps: one in Objective-C, the other one in Swift. Both have: PrefWindow.xib PrefWindow.xib (Base) PrefWindow.strings (German) … The problem is: 1. The Objective-C version just

“Works” means that showWindow does indeed show a window. Yes. After the red button got clicked on the PrefWindow, it never will appear again. The first time prefController is of course nil. The

I would associate a small number of AI with each player. This way, if a player quits, only a few AIs are killed. -- __Pascal J. Bourguignon__

That’s correct. Game Center doesn’t provide any kind of “server side” logic, which is how you’d naturally want to implement AI players. The only thing you can do with a Game Center game

You haven’t really done “due diligence” with this problem description. What does “works” mean? That the window doesn’t reappear after it’s made to disappear? When you call that action

On certain iDevices, we have a UIAlertController that refuses to display the text of the only button, the OK button. This has been a problem for the past year and of course it only appears in the

Is there a corresponding line of code that sets self.prefController to nil when the window is closed? As I understand it, the property will only be set to nil if it is declared as weak, which is most

Have you made sure the “release on close” checkbox isn’t set in IB? (But do you really want the prefs controller to hang around when it’s closed? Seems like a waste of memory to me.) —Jens

https://developer.apple.com/library/content/navigation/index.html#topic=Sample+Code§ion=Resource+Types -- Bill Cheeseman - wjcheeseman@...

It does seem a bit more buried. I entered http://developer.apple.com/samplecode/ and it took me