Invokes a method of the receiver on the specified thread using the default mode.
- iOS 2.0+
- macOS 10.5+
- tvOS 9.0+
- watchOS 2.0+
A Selector that identifies the method to invoke. The method should not have a significant return value and should take a single argument of type id, or no arguments.
The thread on which to execute
The argument to pass to the method when it is invoked. Pass
nilif the method does not take an argument.
A Boolean that specifies whether the current thread blocks until after the specified selector is performed on the receiver on the specified thread. Specify
YESto block this thread; otherwise, specify
NOto have this method return immediately.
If the current thread and target thread are the same, and you specify
YESfor this parameter, the selector is performed immediately on the current thread. If you specify
NO, this method queues the message on the thread’s run loop and returns, just like it does for other threads. The current thread must then dequeue and process the message when it has an opportunity to do so.
You can use this method to deliver messages to other threads in your application. The message in this case is a method of the current object that you want to execute on the target thread.
This method queues the message on the run loop of the target thread using the default run loop modes—that is, the modes associated with the
NSRun constant. As part of its normal run loop processing, the target thread dequeues the message (assuming it is running in one of the default run loop modes) and invokes the desired method.
You cannot cancel messages queued using this method. If you want the option of canceling a message on the current thread, you must use either the
This method registers with the runloop of its current context, and depends on that runloop being run on a regular basis to perform correctly. One common context where you might call this method and end up registering with a runloop that is not automatically run on a regular basis is when being invoked by a dispatch queue. If you need this type of functionality when running on a dispatch queue, you should use
dispatch_after and related methods to get the behavior you want.