Mentally, I have always mapped the presence of an ellipsis to "Puts the
user in a modal state where he has to do something to get back to what
he was doing" -- ie, shows a dialog that the user has to interact with
(if only to exit), but there could be other modal states to be processed
that are not tied to a dialog.
That isn't quite how it is usually used, I realize, but as you note, how
it is usually used isn't consistent.
(Note that the model I used would put an ellipsis on a command which
just puts up a status alert. Because to the user, an alert is a dialog,
no different than the no-op About dialog in what the user has to do
next. Which should encourage use of other status techniques than
mode-forcing alerts!
-- Jim
On 02/15/2010 02:28 AM, sysscore wrote:
i have a question about when i should use ellipsis for commands in
menus, contextual menus and buttons in desktop applications (in
Java).
Sadly, the guidelines of microsoft and mac osx are different about
this topic.
I have found some interesting links in the web but nothing could
answer my questions...
****
Microsoft writtes, that ellipsis should be used, when:
"Proper use of ellipses is important to indicate that users can make
further choices before performing the action, or even cancel the
action entirely. The visual cue offered by an ellipsis allows users
to explore your software without fear.
This doesn't mean you should use an ellipsis whenever an action
displays another window—only when additional information is required
to perform the action. For example, the commands About, Advanced,
Help, Options, Properties, and Settings must display another window
when clicked, but don't require additional information from the
user. Therefore they don't need ellipses.
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."
***
Macintosh writtes, that ellipsis should be used, when the action:
Is performed by the user in a separate window or dialog.
For example, Preferences, Customize Toolbar, and Send Feedback all
use an ellipsis because they open a window (potentially in another
application, such as a browser) or a dialog in which the user sets
preferences, customizes the toolbar, or sends feedback.
To see why such commands must include an ellipsis, consider that the
absence of an ellipsis implies that the application performs the
action for the user. If, for example, the Send Feedback command did
not include an ellipsis, it would imply that feedback is generated
and sent automatically by the application.
***
I think, the rules of mac osx are very easy to understand. But the
rules of microsoft are not. Furthermore, when i check up some
microsoft products, the rules are not respected (e.g. the "Options"
button).
In our application we have for example a non modal dialog, in which
items can be locked or unlocked. The problem is, the user does not
need to be perform the command immediately. But if i named the menu
command "Lock/unlock items" the ellipsis are required, because user
could be expected, that the command will be executed immediately.
In other dialogs, user can managed diefferent presets of specific
settings.
Should i don't use ellipsis only if the command name is
non-ambiguous e.g. "Permission overview" or only information will
be displayed?
Should i use ellipsis, if the user can make some changes (immediately
or not immediately)?
Or must commands named without the verb of the action?
Thanx
________________________________________________________________
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
