You can use the Service Management framework to add items to open at login (though they don't appear in System Preferences > Users & Groups > Login Items, which is a pet peeve of mine). See this

Is there a replacement for LSSharedFileListCreate, LSSharedFileListInsertItemURL &c that have been deprecated in the latest SDKs? Or is there another way to add something to the Finder's sidebar or to

Thankyou both for your replies. I'm as sure as I can be that I'm not creating multiple timers, but I certainly checked for that. I appreciate that this is probably not the best design, due to the

No other response so far… That particular crash is just one example. There are numerous crash reports with the same basic crash, but not always in a CATransaction callback, though that is a very

And that the block isn't being deallocated prematurely somehow. - Jon

Graham - did you ever get a response? This looks to me like you are doing an animation which has completed and is trying to call back to your completion block. For some reason the completion block is

Hi all, We’ve received a number of reports from users of a crash due to a SIGILL as follows: Exception Type: SIGILL Exception Codes: ILL_ILLOPC at 0x7fff32837454 Crashed Thread: 0 Thread 0

It seems to me that this could be regarded as a bug in your design. The consequence of blocking, at a higher conceptual level, is that it destroys the concept of timing which is essential to your

Not knowing how your code is structured, this may be a dumb question, but just to check: Are you certain that you're not creating multiple timers somehow? I've mistakenly done this when creating

Hi all, I’ve been trying to figure out what happened on an overnight run of the code that drives our scientific experiment, and I’m seeing logs that imply that a timer has been firing much more

I’m going to mark this as working now: Set my DocumentController subclass as the main shared NSDocumentController func applicationWillFinishLaunching(_ notification: Notification) { _ =

This works but it’s not right and throws a yucky message let holdDoc = try NSDocumentController.shared.openUntitledDocumentAndDisplay(false) as! Document // set the updated

Hi, I have a metronome app that is able to play audio in the background just fine. It even continues playing when the screens is locked. That is, until the screen goes dark after a few seconds.

I have an App that needs to be upgraded (thanks App Store) and I want the new App to Open and migrate it’s old documents to the new versions document. With the new File Type and Extension. All

I don’t have any detailed list of what changed in Xcode 9.3 that I can share, sorry. Speaking generally, the only changes anyone should notice should be positive; much of the underlying

Any pointers to information on what changed? I looked through the Xcode Release Notes

To answer my own question: textField.stringValue = someString; When I look at the attributedStringValue I see Generic Gray colorspace 1 0.5 So I do: NSMutableAttributedString *mus = [

I have an NSTextField (macOS 13.4, Xcode Version 9.3 (9E145)) which says: textColour Generic Gray colorspace 1 1 backGroundColour NSCalibratedWhiteColorSpace 0 0.4 This, I guess, means all white

The main idea for Cocoa localization is that your source artifacts are the “the truth” for your development region (by default English): You use the real strings in NSLocalizedString() macros and

I have an app (macOS 13.4, Xcode Version 9.3 (9E145)) which was localised (Xcode did some magic for me). Now I made some changes. Is there a way to update the Localizable.string, MainMenu.strings,