Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: NSAlert and threading

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSAlert and threading

Subject: Re: NSAlert and threading
From: Jens Alfke <email@hidden>
Date: Mon, 23 May 2016 18:08:43 -0700

> On May 23, 2016, at 2:41 PM, Fritz Anderson <email@hidden> wrote:
>
> Hence the rule that you don’t do _anything_ lengthy on the main (GUI-runloop) thread. You can see how using a separate thread would solve your problem. Welcome to 2003.

Less dogmatically, you can use -performSelector:withObject:afterDelay:, with a zero delay, to schedule the actual work to take place right after the alert finishes handling the event and closing.

—Jens
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>All threads in app periodically blocked (From: Seth Willits <email@hidden>)
	>Re: All threads in app periodically blocked (From: Seth Willits <email@hidden>)
	>Re: All threads in app periodically blocked (From: Fritz Anderson <email@hidden>)
	>NSAlert and threading (From: Tom Doan <email@hidden>)
	>Re: NSAlert and threading (From: Fritz Anderson <email@hidden>)

Prev by Date: Re: NSAlert and threading
Next by Date: NSDocument not displaying save prompt on dirty document
Previous by thread: Re: NSAlert and threading
Next by thread: Core Data, OutlineView, TreeController
Index(es):
- Date
- Thread