> 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 after the current method/run loop as expired, this
>
> 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 Queue, my question is, is the
> 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 Queue, my question is, is th
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