On Oct 29, 2014, at 12:15 PM, Kyle Sluder <[email protected]> wrote: > On Wed, Oct 29, 2014, at 11:57 AM, Quincey Morris wrote: >> However, this is the wrong solution. A button that doesn’t click through >> should *look* different when the app is in the background (and shouldn’t >> do rollover highlighting). So a better solution is to disable buttons you >> don’t want click-through for, when your app enters the background. > > Huh. I am surprised, but apparently this is precisely what Mail does: > you can't Trash a message in a background window, even if you > Command-click it. > >> 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.
I vote for binding the button's enabled flag to something, then - if the button looks active, nothing's covering the window, and I don't notice the color of the title stoplight, I'm going to be annoyed if nothing happens when I click. _______________________________________________ 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]
