Invokes a method of the receiver on the main thread using the default mode.
- iOS 2.0+
- macOS 10.2+
- 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 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 main thread. Specify
trueto block this thread; otherwise, specify
falseto have this method return immediately.
If the current thread is also the main thread, and you specify
truefor this parameter, the message is delivered and processed immediately.
You can use this method to deliver messages to the main thread of your application. The main thread encompasses the application’s main run loop, and is where the
NSApplication object receives events. The message in this case is a method of the current object that you want to execute on the thread.
This method queues the message on the run loop of the main thread using the common run loop modes—that is, the modes associated with the
common constant. As part of its normal run loop processing, the main thread dequeues the message (assuming it is running in one of the common run loop modes) and invokes the desired method. Multiple calls to this method from the same thread cause the corresponding selectors to be queued and performed in the same same order in which the calls were made.
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.