[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Show/Hide vs Checkbox
From:       Aaron Seigo <aseigo () kde ! org>
Date:       2005-03-30 19:22:28
Message-ID: 200503301922.33175.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On March 30, 2005 18:25, Diego Moya wrote:
> > That's your opinion. I find the current way where the menu action says
> > what's going to happen easier.
>
> Are you sure the menu says what's going to happen?

yes, because we try and maintain a consistent interface where the menu entries 
represent actions: they tell you what they are going to do.

> How do you know 
> whether the menu is showing the current state?

menu entries are actions, they shouldn't be used to indicate state. anyone who 
become confused when reading a verb-based entry such as "Hide Foo" has 
serious issues.

(btw, i really am not a huge fan of the Settings -> Toolbars menu because it's 
state versus verb based.)

> This is a frequent problem arising in buttons (and menu entries *are*
> a kind of button).  A button that change its label according to state
> is always a bad idea, because there is no way to tell whether the
> label shows current state or pressing the button will change the state
> to the one in the label.

good thing we aren't talking about buttons then, but menu entries which are 
inherently actions and use verbs to describe what they are doing.

we obviously use checkboxes in dialogs/windows for these situations because 
they make sense. (one more reason i find toolbars iffy: toggle buttons are so 
common with them)

-- 
Aaron J. Seigo
Society is Geometric

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]