• 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
Re: Crash in AppKit?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash in AppKit?


  • Subject: Re: Crash in AppKit?
  • From: Julian <email@hidden>
  • Date: Sun, 5 Jun 2005 01:31:01 -0400

Yea, that came out wrong, what I meant to say was the timer seemingly was created off the main thread and is thus calling a function on the main thread improperly. I'm tired..

~J
On Jun 5, 2005, at 1:21 AM, j o a r wrote:


On 4 jun 2005, at 21.39, Julian wrote:


Since timers are threaded and you are accessing a GUI component from a different thread(aka thread 4 crashed)


Timers are not "threaded". They're executed in the thread where they were scheduled.


That said, I agree that Jason seem to be accessing things from a non-main thread in a way that's probably not supported.

j o a r




_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Crash in AppKit?
      • From: Jason Staczek <email@hidden>
References: 
 >Crash in AppKit? (From: Jason Staczek <email@hidden>)
 >Re: Crash in AppKit? (From: Julian <email@hidden>)
 >Re: Crash in AppKit? (From: j o a r <email@hidden>)

  • Prev by Date: Re: Crash in AppKit?
  • Next by Date: Non-Editable NSLevelIndicator
  • Previous by thread: Re: Crash in AppKit?
  • Next by thread: Re: Crash in AppKit?
  • Index(es):
    • Date
    • Thread