[Elecraft] SV: K3: Storing PWR level in memories

[Brian Lloyd]

Has anyone defined what the semantics are for a memory location? Are  
you using it as a preset for certain values or are you using it to  
change the state of the radio? I know that when I set a memory for a  
radio I want all of the current state to go into that memory location.  
That would include (but not be limited to) frequency, TX/RX split,  
mode, power, antenna, etc. That way when I select a given memory  
location, everything about the radio is set to how the radio was when  
the memory was stored.

If you only want to change a few things with a "memory" then I think  
what you are talking about is what I would call a preset. I might have  
a preset for mode but not frequency or frequency without changing  
mode. The goal here is to reduce the number of buttons I need to press  
to change operating modes.

So "memory" is not the same thing to all people. It helps to  
understand the semantics of what you mean when you use the word.

If I were driving this from some kind of a computer display attached  
to the radio, when I defined some kind of "memory" location I would  
probably have a series of checkboxes for what changes and what  
doesn't. Basically for each memory I would have a "save/don't-care"  
bit for all the possible parameters. Save means, "what is in the  
memory would overwrite the current setting of the radio." Don't-care  
means, "whatever is currently set into the radio is not changed when  
you recall the memory." That would be very universal. It could also  
prove *very* confusing to the next person using my radio and recalling  
my "memories".

And then there is the question of complexity and confusion. We have an  
excellent example of all the bad things you can do to a user interface  
as a result of "being helpful." Look at the myriad ways one can screw  
up the way Windows is configured! And Microsoft keeps adding more!  
Eventually you reach the point where the UI hinders understanding and  
usefulness.

One of the things that I learned from UI design is that there should  
be very few ways to change something, preferable only one. That way  
the next person can sit down and use the device the same way you did.

Anyway, I would much rather see Elecraft focus on simplicity and  
getting all the base functions to work before branching off into all  
sorts of bells and whistles in the user interface.

(I am still trying to decide if I am going to purchase a K3 for  
myself. It is that or the Flex 5000 and I am still on the fence. I am  
finding all the feedback here *very* enlightening. One good thing  
about waiting -- things get better and cheaper.)

--

73 de Brian, WB6RQN
Brian Lloyd - brian HYPHEN wb6rqn AT lloyd DOT com