菜单项应该始终启用吗？ 你如何告诉用户？
播客上多次讨论的一件事是是否应始终启用菜单项以防止“为什么不可用！” 最终用户的挫败感。
我认为这是一个好主意，但是存在向用户传达缺乏可用性（及其原因）的问题。 还有什么比弹出一个带有文字简介的消息框更好的吗？
当我即将开始开发一个相当大的跨平台 Windows / Mac 应用程序时，我想我应该把它扔掉，听听 SO 人群的智慧。
One of the things that has been talked about a few times on the podcast is whether menu items should always be enabled to prevent "WHY ISN'T THIS AVAILABLE!" frustration for the end user.
This strikes me as a good idea, but then there's the issue of communicating the lack of availability (and the reason why) to the user. Is there anything better than just popping up a message box with a blurb of text?
As I'm about to start on a fairly sizeable cross-platform Windows / Mac app I thought I'd throw this out to hear the wisdom of the SO crowd.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我看到打印机制造商在其打印机属性对话框中所做的一件事是在禁用的项目旁边有一个小帮助气球图标，当鼠标悬停在禁用项目上时会显示工具提示。
您可以对禁用项目执行的另一件事是在括号中添加其被禁用的原因或用户必须执行哪些操作才能启用它。 例如，“保存（已保存）”或“复制（选择要复制的内容）”。
我不喜欢保持它启用，因为这样会让用户在选择任何菜单项时犹豫不决，担心他们只会收到一条错误消息，让他们因为没有意识到自己不能而感到愚蠢。当时可能执行该操作。
弹出对话框的菜单项后面有省略号（...），让用户知道这不仅仅是单击并继续。 必填表单字段具有星号或粗体标签，以避免用户因验证错误消息而受到责备。
One thing I've seen a printer manufacturer do with their printer properties dialog is to have a little help baloon icon beside disabled items that display a tooltip when hovered over.
Another thing you can do with disabled items is to add in parenthesis why it's disabled or what the user would have to do to enable it. E.g., "Save (already saved)" or "Copy (select something to copy)".
I don't like keeping it enabled because then it will instill hesitation in users to select any menu item in fear that they'll just get an error message making them feel stupid for not realizing that they couldn't possibly perform that operation at the time.
Menu items that spring dialogs have elipsis (...) after them to let users know it's not just click and carry on. Required form fields have an asterisk or bold label to spare the user from being scolded with a validation error message.
Joel 有一篇关于该内容的帖子 http://www.joelonsoftware.com/items/ 2008/07/01.html 这可能是开始思考这个问题的好地方。
Joel has a post on that http://www.joelonsoftware.com/items/2008/07/01.html which might be a good place to start thinking about this.
@Bill the Lizard：我将结合 #2 和 #3 - 禁用该项目，但有一个工具提示指示其被禁用的原因。
@Bill the Lizard: I'd combine #2 and #3 - disable the item, but have a tooltip that indicates why it is disabled.
你必须考虑替代方案。
我同意乔尔的观点，#3 似乎是最好的选择。
You have to consider the alternatives.
I agree with Joel on this one, #3 seems like the best choice.