Menu
I've noticed that many Microsoft applications will name some buttons with "..." at the end. These buttons always seem to open up a new dialog. There are some buttons, however, that don't have "...", but do open up new dialog.
For example, in Windows XP, when I open a folder's "Properties" dialog from Windows Explorer, there is an "Advanced..." button under the "General" tab. This button, as expected, opens a new dialog. There is also an "Advanced" button under the "Security" tab. This button also opens a new dialog, but this button doesn't end with "...".
To me, this seems inconsistent, but maybe I'm misinterpreting the meaning. Is there any written guidance for using "..." on buttons?
700
They may also behave differently than if you were using the dedicated arrow keys, or the home, end, insert, etc., keys. This is anecdotal but normally if you tap Ctrl+End where you have a dedicated End key on your keyboard, it takes you to the end of a page or field, or folder.
Solution with the CSS text-align property ¶ It is also possible to align the <button> element to the right by using the CSS text-align property. In the example below, we set the text-align to "right" for the <div> element and use the "left" value of the same property for the <p> element.
When a button group has the “primary right” button, the main actionable button is always in the same place — the right bottom edge of the screen: Actually, if you left-align buttons using the “primary left” rule, the main button will be in the same position as well (but in the left corner instead of the right):
How to add a button at the end of RecyclerView? I want to show a button at the end of RecyclerView. With ListView there was a method addFooterView (), how to do the same with RecylerView. If it is not scrolling, then just add it to your xml. The RecyclerView is dynamically created.
I got ready to quote Microsoft's guidelines for when to use ellipses, but by time time I got here, others had already quoted Microsoft's guidelines, giving answers different than the one I was going to give.
Apparently Microsoft has changed their guidelines, and they don't exactly follow them consistently themselves.
Anyway, the current Microsoft guidelines, as far as I know, are the Windows User Experience Interaction Guidelines (PDF version available here). Regarding ellipses in particular, their guideline is to use ellipses only when the command needs additional information to complete, not merely when the command opens another window. (In part, then, ellipses mean that the command is "safe" to click because it won't immediately do anything.)
So About et al don't need ellipses because they don't need any extra information. Print gets ellipses, because it won't print until you click OK. At least some versions of Microsoft's guidelines explicitly state that Preferences / Options should not have ellipses, because successful execution of the Preferences command only means to show the Preferences dialog, not to necessarily do anything. (This last one seems a bit arbitrary to me.)
100
Yes, the guidance in the Windows Interface Guidelines for Software Designs clearly states that a button or menu item which opens a new dialog should have ellipses "..." appended to it.
It's worth noting that Microsoft products routinely ignore the Microsoft Interface Guidelines.
34
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
