Bug 157984 - Use of "show/hide" vs. checkmarked actions
Summary: Use of "show/hide" vs. checkmarked actions
Status: NEW
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: UI Guidelines (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ui.guidelines-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-20 09:19 EDT by Martin Aeschlimann CLA
Modified: 2022-12-04 15:51 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2006-09-20 09:19:29 EDT
M2

In the Window menu, there's a new item 'Hide toolbar'. When activated, the action is renamed to 'Show toolbar'
Dynamic action labels should be avoided. It complicates the assignment on mnemonics, documentation, shortcut assignment and so on.

A better solution is probably to implement this action as a checked action.
Comment 1 Kim Horne CLA 2006-09-20 10:56:24 EDT
Guideline 3.1 suggests the correct behavior for push and toggle buttons but does not suggest when they should be used.  Changing labels from Show to Hide is common behavior on all OS X apps and I (being a Mac snob) followed that lead.  I've asked for clarification on 3.1 and will proceed based on that.
Comment 2 Susan McCourt CLA 2009-07-15 12:57:30 EDT
I didn't see a blocking UI guidelines bug so I'm moving this to the UI guidelines for clarification/comment.  This can be moved back to platform UI once there is resolution on the guidelines.
Comment 3 Eclipse Genie CLA 2015-01-11 15:58:29 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2017-01-01 14:04:43 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2018-12-23 06:16:59 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2020-12-13 03:44:27 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 7 Eclipse Genie CLA 2022-12-04 15:51:51 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.