Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4331620
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T10:08:12+00:00 2026-05-21T10:08:12+00:00

I know that you can’t update UIView from background view. But not sure if

  • 0

I know that you can’t update UIView from background view.

But not sure if that rule applies when I’m only accessing custom data member variable of UIView descendants.

Suppose I have

@interface MyView : UIView
{ 
NSNumber* number;
}

@property (retain) NSNumber* number;

Here, does accessing the “number” variable from background thread violate the rule “no UIView update from background thread” ?

Thank you

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-21T10:08:13+00:00Added an answer on May 21, 2026 at 10:08 am

    Accessing your subclasses properties in a background thread shouldn’t cause any problems if they are marked as atomic (the default). You have to make sure that you don’t call any UIView methods that cause drawing though.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I know that from iOS 4.0 onwards we can execute our code in background.
I know that we can protect .Net applications from decompiling by using obfuscators. But
I know that it's a subject that can raise a lot of debate, but
I know that JTable can sort by a single column. But is it possible
I know that I can share files using Shared Folders in Virtual PC, but
I know that when you are on shell, the only commands that can be
I know that Android's Youtube app is not open source, but I pulled apart
I know that some website are applications, but not all websites are applications (albeit
I know that a SQL Server full text index can not index more than
Is it only classes inheriting from UIControl that can become first responder? I need

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.