On Nov 6, 2015, at 3:06 PM, Graham Cox <graham....@bigpond.com> wrote: > >> On 6 Nov 2015, at 10:58 AM, Carl Hoefs <newsli...@autonomy.caltech.edu> >> 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 :)
It's an Apple design problem. > having a bunch of endless alerts one after another Who's doing that? > that can asynchronously produce errors, They're not errors, they're alerts. So when Apple pops up an "Allow access to the camera? Yes/No" alert (or a Settings alert, or any others), it squashes any alert from my app that might get presented. Apple design problem. At any rate, I do have the correct paradigm working now, and it accommodates Apple's design flaw. -Carl _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
