On Jul 2, 2008, at 8:42 AM, Rich Rogan wrote:
I'd have to agree with what I believe all this threads comments are
pointing
to (and add that this is what we're doing in our app, with great user
feedback), - it's better to disable a button when this functionality
is not
available then:
1. Hide it, or
2. Leave it visually enabled but thru user intervention the user
discovers
it is actually "disabled".
Actually, no. We've been saying we agree with Joel, that #1 is usually
bad. The best practice we seem to be hovering around is:
Leave the item visible, but visually distinguished as disabled. When
possible, allow for some means to explain why it is disabled (tooltip,
help icon).
Dan
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [EMAIL PROTECTED]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
