• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSThread
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSThread


  • Subject: NSThread
  • From: "Raglan T. Tiger" <email@hidden>
  • Date: Tue, 13 Jan 2015 09:07:58 -0700

I allocate and init an NSThread as follows:

        if ( m_mythread ) [m_mythread cancel];
        m_mythread = [[MYThread alloc] initWithTarget:m_mythread selector:@selector(start) object:m_anobject];
        [m_mythread start];



I set a break in -start and see that this is a separate thread in my process ... so far so good.

But, my UI becomes unresponsive.

I understand that the main thread handles the UI so why would it become unresponsive?

The overall behavior is as if the head code was executing in the main thread.

Can some light be shed on this?

I just did

        [m_bfilenameListFromPath setThreadPriority:0.5];

before

		[m_mythread start];

with the same result :  unresponsive UI, wait cursor (beach ball) is displayed.


-rags



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: NSThread
      • From: Mike Abdullah <email@hidden>
  • Prev by Date: Re: Debugging memory leak in NSURLSession with ARC
  • Next by Date: Re: NSThread
  • Previous by thread: Re: … the actual OpenSSL
  • Next by thread: Re: NSThread
  • Index(es):
    • Date
    • Thread