That list sounds right, Rich, and consistent with the GUI-design guidelines of yesteryear (ahhh...the days when applications were just applications and didn't need a "Web 2.0" moniker to make them sound rich and interactive).
A more generalized rule can be stated: Disable (gray out) options that are sometimes available to a particular user, but not in the current context. Hide options that are never available to a particular user. The latter point is important when considering features to which not all user roles have access. Leaving those showing but disabled can be frustrating. Paul Eisen Principal User Experience Architect tandemseven -----Original Message----- From: Rich Rogan I think we're all saying the same thing, (making my ordered list more organized): Optimal solution: 1. Disable button when functionality is not available, (with messaging). Sub-Optimal solutions: 1. Hide buttons 2. Leave buttons visually enabled but thru user intervention the user discovers buttons are actually "disabled". (There is consensus on the above Optimal solution, right?) ________________________________________________________________ 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
