On May 20, 2016, at 22:48 , Roland King <r...@rols.org> wrote: > > I wondered about this when you first posted about using a custom runloop mode.
I always think runloops are like Fred Flintstone’s feet when he drives his car. There’s something undefinably wrong with the concept, but (I’m led to believe) that’s where running comes from. The problem, it seems to me, is that Graham is trying to *block* the main event loop (except for … what?), and that’s bound to be a bad idea. I think if I was trying to do something like this, I’d look into putting a modal sheet over the window where the replay is happening, which will automatically disable most user actions. (If there are multiple windows affected, it’s fine to put a sheet over each of them. I’ve used this technique to display a progress bar on all windows of a multi-window document. It has the advantage of leaving the uninvolved windows fully functional.) The sheet doesn’t have to be big. It could be more like a badge, and there is API to position it in a non-standard place, if obscuring the activity in the window would be a problem. I guess it all comes down to what (other than menu items, if anything) Graham really wants to lock out. Network activity? Performed selectors? _______________________________________________ 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
