I come here looking for a simple solution, and you try to make me THINK? That’s hardly fair. :-) I managed to move some work onto a different thread, and fix a place where my main thread was

Coming at this from the other side, why does it take enough seconds to get from willFinishLaunching to didFinishLaunching that you care? If you can reduce that time a bit, maybe you don’t have to

I wondered about that myself, and logged out the values of [NSRunloop currentRunLoop] and [NSRunloop mainRunLoop]. They showed the same non-nil value.

Hmph - now that you mention it, there's no current runloop at that point - the app is still launching. So [NSRunloop currentRunLoop] is probably returning nil. You could grabbing mainRunLoop and

Tried that, no change.

Try putting this after your orderFront call: [[NSRunLoop currentRunLoop] runUntilDate:[NSDate dateWithTimeIntervalSinceNow:0.01]]; The runloop basically has to do at least one iteration before the

Yes, I noticed just after I sent it but it might be helpful to someone else. I apologize to the group for the hasty post. -- Frederick "Rick" Bartram bartramf@... PGP key id: 0x4193BED2 key server:

I’m trying to show a splash screen in applicationWillFInishLaunching:, but it doesn’t actually appear until applicationDidFinishLaunching: seconds later. I’ve done all I can think of to make it

Hi Folks, I have an app with a privileged helper tool which needs full disk access in 10.14 Mojave. The privileged helper tool is (as you'd expect) a binary rather than an app bundle, so it's not

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

Take a look at `dispatchPrecondition` to test whether code is executing on a specific queue in a pattern like: func foo() { dispatchPrecondition(condition: .onQueue(mySpecialQueue)) ... } Hope

Thanks a lot. Exactly what I was looking for. (Also: The variant dispatch_assert_queue_debug() is compiled out when the preprocessor macro NDEBUG is defined.) Kind regards, Gerriet.

Comments in the header dispatch/queue.h suggest using dispatch_assert_queue instead.

macOS 13.6 For debugging purposes I want to test that certain methods do run in the correct queue. So: dispatch_queue_t queue = dispatch_get_current_queue(); const char *label =

Well, it does. So if yours does not, rather than go round the houses trying to figure out how to “correct” for that, why not find out why yours isn’t doing what the rest of our apps does do?

Sounds good to me. :)

Are you using an assets file (xcassets) for your app icon? If you make an icon asset in an xcassets file it should contain a slot for that icon at all sizes.

There also should be a special size for the small alert icon within your app’s icon xcassets file.

I failed to find this. Probably missed something obvious. But I stumbled upon: NSRunningApplication *currentApplication = NSRunningApplication.currentApplication; NSImage *myAppImage =

Yes it should. Also: the documentation says, it does. But sadly it does not.