"Drew Adams" <[EMAIL PROTECTED]> writes: > The State button in Customize is not a button but a pulldown list > (menu).
Your observation applies to the Value Menu as well. Sounds like changing the text of the State menu from State to State Menu would be a good choice as long as the widget still looks like a button. > In general, however, pulldown menus are not a good UI idea. Disagree in general. They are fine in menu bars and context menus. > Because it is too easy to not notice that they are menus (i.e > represent choices). I agree. The menus should not look like buttons. I am at a loss of how to make a standalone menu though as menus are usually associated with menu bars. And these are menus, not comboboxes, since they perform actions, not just represent choices. Now that I think of it, the Value Menu is not a menu, but a combobox. Oy, we probably should postpone creating different widgets for menus and comboboxes until after the release. > It is a bad idea for the closed state of a menu to > represent one of the possible menu choices. True, but you'd use a combobox widget in this case and it doesn't apply to the State menu anyway. -- Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. _______________________________________________ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
