Re: Question about the Main Thread

> On Apr 25, 2017, at 4:37 PM, Charles Srstka wrote: > >> On Apr 25, 2017, at 9:51 AM, Dave wrote: >> >> Mac Project. >> >> Hi All, >> >> I’m using performSelector: withObject: afterDelay: in order to postpone >> further processing until

Re: Question about the Main Thread

> On Apr 25, 2017, at 9:51 AM, Dave wrote: > > Mac Project. > > Hi All, > > I’m using performSelector: withObject: afterDelay: in order to postpone > further processing until after the current method/run loop as expired, this > puts the request at the End of the

Repository of older (outdated) PDF Guides?

I've googled til my fingers are black and blue, but no luck finding some of the older PDF guide documents. I could never express in words how disappointed I am that Apple discontinued producing readable documentation - I use to crow about it to all my non-Apple dev friends. Anyway, does

Re: Question about the Main Thread

> On Apr 25, 2017, at 7:51 AM, Dave wrote: > > Mac Project. > > Hi All, > > I’m using performSelector: withObject: afterDelay: in order to postpone > further processing until after the current method/run loop as expired, this > puts the request at the End of the

Question about the Main Thread

Mac Project. Hi All, I’m using performSelector: withObject: afterDelay: in order to postpone further processing until after the current method/run loop as expired, this puts the request at the End of the Queue, my question is, is there anyway of putting it at the head of the Queue so it gets