performSelectorOnMainThread: vs dispatch_async on main queue

最新推荐文章于 2024-06-28 00:15:00 发布

yitailong

最新推荐文章于 2024-06-28 00:15:00 发布

阅读量1.6k

点赞数

分类专栏： IOS 文章标签： ios iOS IOS

IOS 专栏收录该内容

13 篇文章

订阅专栏

本文深入探讨了Objective-C与Swift两种编程语言在iOS开发领域的应用与区别，详细对比了它们的语法特点、性能优势以及生态系统，帮助开发者做出更适合项目的语言选择。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

By default, -performSelectorOnMainThread:withObject:waitUntilDone: only schedules the selector to run in the default run loop mode. If the run loop is in another mode (e.g. the tracking mode), it won't run until the run loop switches back to the default mode. You can get around this with the variant -performSelectorOnMainThread:withObject:waitUntilDone:modes: (by passing all the modes you want it to run in).

On the other hand, dispatch_async(dispatch_get_main_queue(), ^{ ... }) will run the block as soon as the main run loop returns control flow back to the event loop. It doesn't care about modes. So if you don't want to care about modes either, dispatch_async() may be the better way to go.

转载：http://stackoverflow.com/questions/9335434/whats-the-difference-between-performselectoronmainthread-and-dispatch-async-on-m