On Mon, 1 Aug 2005 12:45:10 Richard Frith-Macdonald wrote:
[...]
No ... runloops are meant to be thread-local, and it's not safe to
monitor a runloop running in one thread from an other thread.
If you want a notification when there are no more inputs for a
runloop, you can just use
On 2 Aug 2005, at 07:52, Chris Vetter wrote:
On Mon, 1 Aug 2005 12:45:10 Richard Frith-Macdonald wrote:
[...]
No ... runloops are meant to be thread-local, and it's not safe to
monitor a runloop running in one thread from an other thread.
If you want a notification when there are no more
Hi there,
I need to create a runloop that's supposed to run for X minutes. Naturally,
-runUntilDate: comes to mind. So far, so good.
My question is whether there is an appropriate method to get some/any kind
of 'notification' that the runloop has stopped. I do not really care whether
it stops
On 2005-08-01 08:12:37 +0100 Chris Vetter [EMAIL PROTECTED] wrote:
Hi there,
I need to create a runloop that's supposed to run for X minutes. Naturally,
-runUntilDate: comes to mind. So far, so good.
My question is whether there is an appropriate method to get some/any kind
of 'notification'
On 1 Aug 2005, at 11:04, Chris Vetter wrote:
On Mon, 01 Aug 2005 08:53:23 Richard Frith-Macdonald wrote:
Maybe this has an obvious answer but if so I can't see it... :-(
The documentation for -runUntilDate: says
Runs the loop in NSDefaultRunLoopMode by repeated calls to
