Re: How to get the dispatch queue for the current thread's runloop?
Re: How to get the dispatch queue for the current thread's runloop?
- Subject: Re: How to get the dispatch queue for the current thread's runloop?
- From: Marco Tabini <email@hidden>
- Date: Fri, 27 Jan 2012 16:19:26 -0600
On 2012-01-27, at 2:14 PM, Jens Alfke wrote:
> I'm really used to using -performSelector:withObject:afterDelay: to make something happen later. But I'd much rather use a block than a target/action. I can't find any API for this, however. Am I missing something? What I want is basically like
> PerformBlockAfterDelay(^{ …code here…}, 5.0);
>
> It looks like I should just call dispatch_async, but I'm unsure which dispatch queue to use. dispatch_get_main_queue only works for the main thread. Can I use dispatch_get_current_queue? I'm unsure of what this does when called on a background thread. The API docs say "If the call is made from any other thread, this function returns the default concurrent queue" … is that a queue associated with the thread's runloop, that's guaranteed to execute tasks on that thread?
I just use a little category on NSObject that I think I pulled from somewhere—but I can't remember where from:
#pragma mark -
#pragma mark Delayed block execution
- (void) performBlock:(void (^)(void)) block afterDelay:(NSTimeInterval) delay {
block = [block copy];
[self performSelector:@selector(fireBlockAfterDelay:)
withObject:block
afterDelay:delay];
}
- (void)fireBlockAfterDelay:(void (^)(void))block {
block();
}
This is pretty old code (it relies on ARC, though), so there might be a better way to do it these days.
—Mt.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden