Is it wrong for a context (right click) menu be the only way a user can perform a certain task?

Posted by Eric on Stack Overflow See other posts from Stack Overflow or by Eric
Published on 2010-06-14T20:53:34Z Indexed on 2010/06/14 21:02 UTC
Read the original article Hit count: 129

I'd like to know if it ever makes sense to provide some functionality in a piece of software that is only available to the user through a context (right click) menu. It seems that in most software I've worked with the right click menu is always used as a quick way to get to features that are otherwise available from other buttons or menus.

Below is a screen shot of the UI I'm developing. The tree view on the right shows the user's library of catalogs. Users can create new catalogs, or add and remove existing catalogs to and from their library. Catalogs in their library can then be opened or closed, or set to read-only.

Screen Shot

The screen shot shows the context menu I've created for the browser. Some commands can be executed independently from any specific catalog (New, Add). Yet the other commands must be applied to a specifically selected catalog (Close, Open, Remove, ReadOnly, Refresh, Clean UP, Rename).

Currently the "Catalog" menu at the top of the window looks identical to this context menu. Yet I think this may be confusing to the users as the tree view which shows the currently selected catalog may not always be visible. The user may have switched to the Search or Filters tab, or the left pane may be hidden entirely.

However, I'm hesitant to change the UI so that the commands that depends on a specifically selected catalog are only available through the context menu.

© Stack Overflow or respective owner

Related posts about best-practices

Related posts about user-interface