On Sun, Jan 25, 2009 at 12:47 PM, David Hoerl wrote:
> Thanks to those who have posted on this, and suggested workarounds. However,
> in a simple non-threaded app, this call should work, no? And perhaps the 0
> time timer would also suffer the same fate.
Well as I said, the documentation says tha
Thanks to those who have posted on this, and suggested workarounds.
However, in a simple non-threaded app, this call should work, no? And
perhaps the 0 time timer would also suffer the same fate.
The project has a checkbox so the user can enable the CFWakeup.
To convince myself this was not ca
On Sat, Jan 24, 2009 at 11:07 PM, Adam R. Maxwell wrote:
>
> On Jan 24, 2009, at 10:18 PM, Michael Ash wrote:
>
>> On Sat, Jan 24, 2009 at 3:42 PM, David Hoerl wrote:
>>
> [...]
>
>>> The current app is single threaded.
>>>
>>> Can anyone shed any light on why the CFRunLoopWakeUp() call is necess
On Jan 24, 2009, at 10:18 PM, Michael Ash wrote:
On Sat, Jan 24, 2009 at 3:42 PM, David Hoerl wrote:
[...]
The current app is single threaded.
Can anyone shed any light on why the CFRunLoopWakeUp() call is
necessary? Is
there some other issue I'm missing?
Look at the big master list
On Sat, Jan 24, 2009 at 3:42 PM, David Hoerl wrote:
> I have a few hundred tasks to handle, and am using NSRunLoop's
> performSelector to get the scheduled:
>
> -(void)nextTask:(SEL)sel
> {
> [[NSRunLoop mainRunLoop] performSelector:sel target:self argument:nil
> order:0
>modes:[NS
On Sat, Jan 24, 2009 at 2:42 PM, David Hoerl wrote:
> I have a few hundred tasks to handle, and am using NSRunLoop's
> performSelector to get the scheduled:
>
> -(void)nextTask:(SEL)sel
> {
> [[NSRunLoop mainRunLoop] performSelector:sel target:self argument:nil
> order:0
>modes:[NS
I have a few hundred tasks to handle, and am using NSRunLoop's
performSelector to get the scheduled:
-(void)nextTask:(SEL)sel
{
[[NSRunLoop mainRunLoop] performSelector:sel target:self argument:nil order:0
modes:[NSArray arrayWithObject:NSDefaultRunLoopMode]];
CFRunLoopRef crf =
