Home/ Questions/Q 4381542
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T12:39:45+00:00

I know and heard most UI related shouldn’t be done in thread other than

  • 0

I know and heard most UI related shouldn’t be done in thread other than main.
I also know that you can update non-view related data member(that you added) of UIView derived class.

I wonder if the below operations are fine or not to do in background thread.

  1. allocing UIView
  2. init UIView with/without(CGRectZero or just init) frame info
  3. modifying frame/image(UIImageView’s) property of UIView
  4. modifying image property of NSObject derived class. (treating UIImage as data)
  5. accessing subviews with subviews method
  6. etc.. Is there a well defined documentation on this issue?

Thank you

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You shouldn’t be doing anything view related in a background thread. All of the items you listed should not be done in a background thread. If you’re breaking your app up correctly for MVC, the view should only contain items that dictate how it is displayed. So anything relating to one should only be in the main thread.

    All of your data manipulation should be residing in your model. It can be threaded as needed for performance. Just be careful that you send any messages to update the UI for the data manipulation on the main thread. This includes notifications. They gets sent on the same thread they were created on. So it’s easy to forget to switch into mainThread when sending one.

    • 0