Re: Blocking Method Return
Re: Blocking Method Return
- Subject: Re: Blocking Method Return
- From: "I. Savant" <email@hidden>
- Date: Fri, 2 Dec 2005 11:14:50 -0500
Josh:
In case it wasn't clear, the reason it's not a good idea to block
the main thread is because this leaves no option for a 'cancel'
button that actually listens for a click ... or indeed any standard
UI way of quitting the application failing a cancel button beyond
force-quitting/terminating the app in a very unfriendly way. This is
*NOT* good design in any case.
The main thread listens for events and passes them on to the
appropriate 'thing'. In the case of waiting for a network operation
to return, what about a timeout? What about an incomplete response?
This leaves no option for the user to click a Cancel button (even if
one is there and wired in) if the operation is taking too long. This
leaves no 'out' for the user. Bottom line: Bad design = user
frustration.
--
I.S.
On Dec 2, 2005, at 11:09 AM, j o a r wrote:
Regardless, it's certainly not an argument against windows apps.
It certainly is an argument against any app that uses networking
and that doesn't use threads while waiting for network operations
to return...
_______________________________________________
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