何时在菜单项后使用省略号
在几乎所有具有菜单栏的应用程序中，有些项目后面有省略号 (...)，有些则没有。 关于何时放置省略号以及何时不放置是否有一个众所周知的约定？ 你什么时候做？ 你做吗？
我查看了各种 Windows 应用程序，这就是我的结论：
省略号
- 打开需要用户输入才能执行某些操作的表单的菜单项（替换、转到、字体）
无省略号
- 仅执行某些操作的菜单项（剪切、粘贴、退出、保存）
- 打开不需要用户输入的表单的菜单项（“关于”、“检查更新”）
）似乎总是有不遵循此规则的菜单项。 例如，Visual Studio 中的帮助项（如何、搜索、索引）以及查找和替换（快速查找、在文件中查找、查找符号）。
因此，经过更多思考后，我现在认为可能是这样的：
省略号
- 肯定会打开模式窗口的菜单项。
无省略号
- 打开非模式窗口的菜单项。
- 不打开任何窗口的菜单项。
- 很可能不会打开模式窗口的菜单项（例如“保存”，如果您之前没有保存过或类似的内容，它会打开模式窗口，但否则不会）
你们觉得怎么样？
In pretty much all applications that have a menu bar, some of the items have an ellipsis (...) after them, and some don't. Is there a well known convention on when to put that ellipsis there and when not to? When do you do it? Do you do it?
I have looked at various windows applications, and this is what I have come to:
Ellipsis
- Menu items which opens a form that require user input to do something (Replace, Go to, Font)
No ellipsis
- Menu items which just does something (Cut, Paste, Exit, Save)
- Menu items which opens a form that does not require user input (About, Check for Updates)
But then there always seems to be menu items that doesn't follow this rule. For example the Help items (How do I, Search, Index) and the Find and Replace (Quick Find, Find in Files, Find Symbol) in Visual Studio.
So after thinking about it a bit more I now think this might be the thing:
Ellipsis
- Menu items that will definitely open a modal window.
No Ellipsis
- Menu items that opens a non-modal window.
- Menu items that doesn't open any window.
- Menu items that most likely won't open a modal window (Like Save, which does open a modal window if you haven't saved before or something like that, but otherwise don't)
What do you guys think?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
关键因素是菜单选项在执行操作之前是否需要附加信息（输入或选择）。 因此，Help-About 不需要省略号，但 File-Open 需要。 不管怎样，微软、苹果和 KDE 指南都是这么说的。
Microsoft Windows 应用程序应该遵循微软的“用户体验指南”。 以下是他们对菜单项上的省略号的看法。
David 的回答引用了 KDE 3 用户界面指南，
Apple 人机界面指南 说：
旧版本的 HIG 更详细，并给出了示例：
The crucial factor is whether the menu option requires additional information (input or a selection) before it carries out the operation. So Help-About doesn't require an ellipsis, but File-Open does. That's what the Microsoft, Apple and KDE guidelines say anyway.
Microsoft Windows applications are supposed to follow Microsoft's "User Experience Guidelines". Here's what they say about ellipses on menu items.
David's answer cites the KDE 3 user interface guidelines,
The Apple Human Interface Guidelines say:
Old versions of the HIG went into greater detail, and gave examples:
据我了解，(...) 结束通常意味着用户将被要求提供一些输入。 没有（...）意味着不需要输入。
As far as I understand this, (...) a the end usually means that user will be asked for some input. And no (...) means that no input is needed.
你说得对，这就是总结。 如果您想了解更多信息，可以在此处找到用户风格指南列表： http://www.experiencedynamics.com/science-usability/ui-style-guides
You're right, that about sums it up. If you want to know more, you can find a list of User Style Guides here: http://www.experiencedynamics.com/science-usability/ui-style-guides
我同意，这与我自己对何时包含省略号的看法相当吻合。
我想省略号的目的是“警告”用户，以便她能够理解某个选择是可以安全探索的，如果不通过对话框询问更多信息，它不会立即执行某些操作。
在某些程序中，例如（至少是旧版本）Autodesk 的 Maya （高端 3D 建模包），省略号实际上是一个小对话框图标。 您可以单击菜单中的图标来获取图标，或者单击菜单项的其余部分（文本）以使用与上次相同的设置或类似的设置重复该命令。 看来这个想法并没有流行起来并成为主流。
I'd agree, that matches my own perception of when to include the ellipsis fairly well.
I guess the point of the ellipsis is to "warn" the user, so that she can understand that a certain choice is safe to explore, it won't immediately do something without asking for more information through a dialog.
In some programs, like (at least older version of) Autodesk's Maya (a high-end 3D modelling package), the ellipsis was actually a small dialog-icon. You could click the icon, in the menu, to get the icon, or click the rest of the menu item (the text) to repeat the command with the same settings as last time, or something like that. It seems that idea didn't catch on and become mainstream.
这确实是一个非常棘手的问题。 乍一看，这似乎是显而易见的，但有许多操作属于这些类别之间。 有趣的是，微软自己也违反了这一做法。
Vista 中的示例
在计算机管理菜单文件 - 选项...中有省略号
在计算机管理/用户和组/用户中。 右键单击用户。 新用户...操作有省略号，但重命名没有，尽管它需要额外的操作来实际重命名帐户。
在 Micrsoft SQL Server Management Studio 菜单“文件 - 打印”中具有带有省略号的“属性...”按钮。
这只是经过 5 分钟的调查。 还有很多例子。
您可以为这两种行为主张两种约定。 如果不在显示的对话框中执行一些额外操作（假设应使用省略号），则实际上无法更改任何属性或选项。 但是，您可能只是想查看定义了哪些选项或属性，并且假设没有使用省略号。 微软还承认，在某些情况下存在歧义
“如果存在歧义（例如，命令标签缺少动词），请根据最可能的用户操作来决定。如果只是查看窗口是常见操作，则不要这样做使用省略号。” 然而，基于此，对选项和属性使用省略号会更有意义，因为您更有可能想要更改仅查看它的属性。
This is a very tricky question indeed. At first had it might seem obvious but there are many actions that fall between the categories. It is interesting to see that Microsoft themselves violate this practice.
Example from Vista
In Computer Management menu File - Options... has ellipsis
In Computer Management / Users and Groups / Users. Right-click a user. The New user... action has ellipsis but Rename does not although it requires extra actions to actually rename the account.
In Micrsoft SQL Server Management Studio menu File - Print has Properties... button with Ellipsis.
This is just after 5 minutes of investigating. There are plenty more examples.
You can argue for both conventions for both these actions. You can't actually change any properties or options without doing some extra actions in the dialog that is displayed which assumes that ellipsis should be used. However you might just be interested in viewing what options or properties that are defined and that would assume that no ellipsis is used. Microsoft also acknowledge that there are instances when there is ambiguity
"In case of ambiguity (for example, the command label lacks a verb), decide based on the most likely user action. If simply viewing the window is a common action, don't use an ellipsis." However based on this it would make more sense to have ellipsis for Options and Properties as it is probably more likely that you want to change a property that just view it.