Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
- Subject: Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
- From: Brian Lambert <email@hidden>
- Date: Wed, 14 Mar 2012 09:07:27 -0700
Scott, it's not that any one thing is hard to get correct. Arrogantly
calling someone stupid, as you've done here, doesn't help. It's
the subtlety of getting *everything* correct. A GUI system, and the
programs that are layered on top of it, embody a great deal of complexity.
Allowing multiple threads to operate on the GUI causes this complexity to
permute.
On Wed, Mar 14, 2012 at 6:43 AM, Scott Ribe <email@hidden>wrote:
> On Mar 13, 2012, at 3:09 PM, JongAm Park wrote:
>
> > In other words, the thread function may want to update UI like inserting
> a log message to a text field on a window and thus asking main thread to do
> so, and main thread is waiting to acquire a lock or waiting using "Join",
> then either the main thread and the other thread can't progress.
>
> Ouch. If you think that's a problem, then trust me, you would really make
> a mess with multiple UI threads.
>
> --
> Scott Ribe
> email@hidden
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
>
>
>
>
> _______________________________________________
>
> 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
>
_______________________________________________
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