On Oct 29, 2014, at 12:15 , Kyle Sluder <[email protected]> wrote: > >> Dangerous things should be undoable or have a confirming alert anyway. > > Steve writes music software. To pick an example, disabling recording on > an active input track should NOT require a confirmation alert, even > though it's a destructive action.
Sorry, I was a bit lazy in what I said. I agree that there are cases where the button shouldn’t work in the background, and even undo or a confirming alert aren’t a good way of dealing with buttons that *shouldn’t* (for separate reasons) be enabled in the background. I think I was trying to say that disabling seems justifiable only in a minority of cases, not routinely. I also wanted to emphasize my agreement with the sentiment (expressed in a couple of posts) that there’s an issue of what we who’ve used Macs since the very old days have *trained* ourselves to expect. It’s worth remembering that even back then, background Unix windows (in X11 or whatever) were active, and Unix users used to laugh at us for having disabled background windows, and the world didn’t end just because they did it their own way. _______________________________________________ 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]
