The OP was calling -[NSFileManager enumeratorAtPath:], which is an old API that predates NSError, so failing silently is all it can do. (Cocoa APIs do not throw exceptions except in the case of progra

No, I’ve used it with MP3 and AAC and AIFF; I’m pretty sure it supports every format there’s a system codec for (i.e. most audio formats except Ogg and FLAC, but you can get 3rd party components to do

AVFoundation has a higher-level OOP API for this. Look for methods for accessing metadata, and constants defining the various metadata types like Title, Artist, etc. —Jens

Those are JavaScript escape sequences. If you’re reading raw JS string literals out of the page, you need to decode all the escapes, which are like the C ones plus \uxxxx. This isn’t anything to do wi

You want NSDateComponentsFormatter: /* NSDateComponentsFormatter provides locale-correct and flexible string formatting of quantities of time, such as "1 day" or "1h 10m", as specified by NSDateCompon

Nope. This is due to the way CF bridging works — the magic class __NSCFArray (?) is bridged to CFArray and CFMutableArray. To support mutable arrays, that means __NSCFArray has to subclass NSMutableAr

That’s the behavior I was getting the last time I worked on this app, a few months ago, but it’s somehow stopped working and I can’t get it to work again. Specifically, what used to work was 1. Click

I think that reply was meant for a different thread? —Jens

I’ve got a view-based NSTableView that uses NSTextFields. I’d like to be able to select text in some of the columns, mostly so it can be copied to the pasteboard. If I set the “selectable” property of

Same as it ever was — just implement the -application:openFile: method in your app delegate. You also need to edit your Info.plist to include the document types your app knows how to open. To my knowl

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 we

It’s in the crash report near the top, like this: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 That long hex number is the address. —Jens

Not exactly. In frame 4 the NSInputStream has been messaged successfully, which almost never happens if it’s already dealloced; you almost always get a crash in objc_msgsend in that case. Instead it l

The only reason I can think of that the first two attempts wouldn’t work is that the main thread’s runloop is blocked, so it can’t process queued blocks. Are you by chance doing something on the main

NSLinguisticTagger provides a lot of operations like finding word boundaries and identifying parts of speech. I don’t know if it can be made to identify English words without spaces between them.* App

Xcode stopped supporting the GNU C++ lib a few releases ago. You’ll need to use Clang’s libc++ instead. Hopefully there should be few compatibility problems. —Jens

I build a lot of C++ and I don’t think I’ve ever seen that. Are you overriding the header search path or specifying any exotic compiler flags already? And double-check that you’ve got a valid SDK sele

Not as far as I know. In general, it’s a bad idea to use this sort of “hidden” RPC across a network. Networking is fundamentally unlike local function calls, and making a network call look exactly lik

That may be Swift-only … it doesn't show up in the 10.14 SDK headers. (Gerriet is using Obj-C, as indicated by his code snippet.) —Jens

I do the same thing (in an app I've been tinkering with for years), but it's a dead end. WkWebView runs the WebView in a separate process, for security reasons, which means its DOM objects are complet