On Thu, Apr 30, 2009 at 3:31 PM, Ken Tozier wrote:
>
> On Apr 29, 2009, at 11:48 PM, Michael Ash wrote:
>
>> Seems like you're adding a lot of complication for what is essentially
>> a continually running operation. Instead of that, why not do this?
>>
>> 1. Spawn a thread.
>> 2. Sample files.
>>
On Apr 29, 2009, at 11:48 PM, Michael Ash wrote:
Seems like you're adding a lot of complication for what is essentially
a continually running operation. Instead of that, why not do this?
1. Spawn a thread.
2. Sample files.
3. Sleep.
4. Goto 2.
Or, in code:
- (void)threadMethod {
while(1)
On Wed, Apr 29, 2009 at 9:55 PM, wrote:
> Hi
>
>
> I wrote a directory scanner application that spawns 4 different threads with
> independent rescan intervals and need to repeat the process if and only if a
> thread has completed a scan. Basically, for each file type I'm watching, the
> proces
2. Wait until the thread completes
NSThreadWillExitNotification?
-- GG
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)list
On Wed, Apr 29, 2009 at 8:55 PM, wrote:
> I tried calling NSObject's
>
>
> performSelector:(SEL) aSelector withObject:(id) anArgument afterDelay:(
> NSTimeInterval ) delay
>
>
>
> But the receiver's " aSelector" method is never getting called. The only
> logical place to perform this sched
* You could use NSOperationQueue and set the maximumThread count to 1.
and make for each of these methods an NSOperation. And then add those
4 operations to your OperationQueue.
* But your case is simple so you can easily code this your self by
creating an object for each operation you are
