> On Oct 29, 2014, at 10:57 AM, Quincey Morris > <quinceymor...@rivergatesoftware.com> 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.
+1. This is what the 'classic' OS (Mac OS ≤ 9) did. That way you could tell whether a button was directly pressable or not. (The downside was increased flicker / visual noise when switching windows.) >> 1. Only rarely do I find it expected and useful. Otherwise, it's not good >> user experience. > > You’re generalizing based on … personal preference? +1 again. Steve, be wary of disabling long-established system-wide UI behaviors in your app just because you _personally_ dislike them. Chances are there are a lot of users who do like them, or at least have learned them subliminally, and may be confused/annoyed when they for some reason don't work in your app. Anecdotally, a lot of casual/inexperienced users don't really understand the distinction between active and inactive windows, especially when the windows aren't overlapping. So having buttons work differently based on that distinction is likely to be confusing to them. That was one of the reasons the original Aqua UI design deliberately changed the behavior of controls to leave them enabled in non-active windows. —Jens _______________________________________________ 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
