Alex Zavatone via Groups.Io wrote on 21/4/19 12:16: That doesn't work, either. I was trying to force it bottom-up (I thought that the next responder would automatically be made first), but it seems to

Sorry if this is too late, but isn’t there a resignFirstResponder that you could call on the text field? Cheers, Alex Zavatone

Hi Folks, I will dispense with a rant about the eroding freedoms and the pains of sandboxing. My problem is finding a correct (App Store approval) method to enable drag and drop to the App

Thanks, that was it. John Jeremy Hughes via Groups.Io wrote on 18/4/19 12:55: -- John Brownie Mussau-Emira language, New Ireland Province, Papua New Guinea Kouvola, Finland

I think you should be calling (NSWindow) makeFirstResponder. Jeremy

I implemented a new feature that brings up an NSTextField for entering data. Once it's done, I call removeFromSuperview() and it goes away as expected. But then validateUserInterfaceItem is no longer

The document you cite is about Key Value Coding, not about Objective-C properties. The latter are not implemented using the former. If a @property declaration specifies a getter or setter method, the

Alex; I think you may be going down the wrong path on this one. It sounds more like a second instance is being created somehow. Did you guard the init method so that no one can create a second one,

Yes, unfortunately, that is the correct behavior. This is described

At the runtime level, properties are implemented as getter and/or setter methods. The `getter=` syntax just lets you rename the getter method. It doesn’t affect the property name. It seems a little

I just replicated this in a sample and ran a short test to see what the results are. @interface MyObject : NSObject @property(strong, nonatomic, readwrite,getter=getRootAPIData) NSDictionary

In the iOS app that I’m working on now, we have a problem that I’ve never seen in my years as an iOS programmer. While we have a 99.7% crash free user experience, what does crash is weird as

There are other NSPanels, that’s not sufficient. What I came up with was to find an array of visible windows before calling orderFrontStandardAboutPanel:, find an array of visible windows

True, but this is a little freeware side project, and I didn’t feel like polishing that much.

Where is it documented that it's wrong? I don't think it's actually wrong. iMovie, for example, has com.apple.iMovieEvent declared both as an exported UTI and as a document type. Besides, it *does*

Well, this is kind of wrong. CFBundleTypeExtensions and LSTypeIsPackage should not be specified in the document type when you’re using an exported UTI. I don’t really recall their presence

I have a file type all set up in my target's Document Types and Exported UTIs as

The About window has no name - the title is blank. it would seem that a more interesting way to do the would be to use the [NSWindow windowNumberWithOptions:] method, which does return an array of

Ah, fair point! How hard is it then to make your own About box? To bring it up instead of the prebuilt one is a very small change to the ‘About’ menu item, to target a different method. Making

Well, its class is NSPanel rather than NSWindow - is it sufficient to just hide / show all NSPanels in the app's window list when you're deactivated / activated? Alternately, you can look at all