开云体育

I suggest that all buttons that can change state
- show the state that they will change TO, which is what we expect when we see a button of any sort to press

TRANSFORM ON - should turn on transform
MODE MS5351 - should enable MS code
PAUSE SWEEP - should pause the sweep, and //there should be no check box// The box is superfluous, because the button text provides context, and the box is confusing because its check state is not clear.

I might have missed some.

I have thought of this as well, but what they have done actually follows
the practice used on many commercial test instruments. I would like to see
them make the box green if on or gray if not. However, I realize that many
color blind operators would not benefit from that.

On Fri, May 13, 2022 at 10:12 AM Rich NE1EE <TheDustyKey@...>
wrote:

I suggest that all buttons that can change state
- show the state that they will change TO, which is what we expect when we
see a button of any sort to press

TRANSFORM ON - should turn on transform
MODE MS5351 - should enable MS code
PAUSE SWEEP - should pause the sweep, and //there should be no check box//
The box is superfluous, because the button text provides context, and the
box is confusing because its check state is not clear.

I might have missed some.

--
Eric M. Gildersleeve ~ KD7CAO
Google Voice: 940-784-3029

On 2022-05-13 11:00:-0500, you wrote:

I have thought of this as well, but what they have done actually follows
the practice used on many commercial test instruments. I would like to see
them make the box green if on or gray if not. However, I realize that many
color blind operators would not benefit from that.

I don't think that we are using the same device! :-)
1. The MODE button shows what IS selected, not what WILL BE selected.
2. TRANSFORM OFF mean that it is OFF.
These are the reverse of what I suggest.
3. BUT...PAUSE SWEEP is the reverse of these!!! I suspect that is because originally it had check box, and now it has a text state change. But the confusing part is that it is reversed from the other 2.
I just happened to be using these today, and thought to write, but there might be others.

I think that it makes sense for the button text to change to what the button /will do/, but I am open to other ideas.

Perhaps you could be more specific about commercial test instruments?
I'm happy w color changes, too. I worked on an international project a short time ago, and we all agreed that we needed to have a 'color-blind' standard. We researched the options, and came up with a good range of colors.

Th H4 currently uses green to show that the selected cal is not the saved cal...something, such as the freq range, has changed. And when it is green, if you tap it, you get back the saved cal state. It could just as easily be a * on the button, just like in an editor. Again, I don't have a specific standard in mind. I would like to see the UI behave the same for every button.