> On 6 Nov 2015, at 10:58 AM, Carl Hoefs <[email protected]> wrote: > > (As a general thought, though, it would appear that UIAlertController > should be a singleton app-wide, and it should manage its own serialized > presentation. Any other solution seems like external plumbing to fix a > design problem.)
It is a design problem - yours :) From a usability point of view, having a bunch of endless alerts one after another must surely be one of the quickest ways to make your users hate your app and you in turn. If you have a bunch of threads that can asynchronously produce errors, why not simply queue the errors, or info about them, silently, then when the work as a whole completes, present one alert (on the main thread) that says that some of the work could not be completed, and gives the user the option to go into more detail, where you would use the queued error information to populate a list of errors and what the user can do about them. If the user can’t do anything about them, then there’s probably no point going into even that much detail. —Graham _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
