> Providing an optional means of reinforcing split/non-split state is > in the tradition of design iteration -- using feedback about real > errors that people make, then minimizing them. That's why we're > having this conversation.
The problem is that you're still trying to reinforce a negative. The normal operation is simplex - none of the additional indicators will do anything to reinforce to an operator set for simplex that he *should be* split. These indicators only work if the operator *knows he should be split* and if he knows that the current indicators - three on the K3, two in the P3 - are enough to let him know that split is engaged. Even experienced operators can get distracted. It is not the lack of sufficient indicators that is the distraction - it is not thinking before pressing the PTT switch and even the best can forget to look before transmitting.
And while I'd love to add a dozen more LEDs, a klaxon horn, and a Van de Graf generator to the K3's user interface, we have to work within the limits of the existing hardware.
Unfortunately those are all static indications *when split is engaged* - they still do not (and can not) tell the operator that split *should* *be* engaged when it is not. The only real solution is signal decoding that listens for "UP" and automatically engages split. 73, ... Joe, W4TV On 2015-02-18 11:00 AM, Wayne Burdick wrote:
User interface design is often called upon to make up for human failings. We get distracted, we forget, we have trouble breaking bad habits, we easily acquire new ones. This is true no matter how much training we have. The designer tries to take such issues into account up front, but sometimes we find out later and make adjustments. My cognitive science professor, Don Norman, put a heavy emphasis on embedding knowledge "in the world." Signs and indicators need to be as unambiguous as possible to help those of us who can't or won't pay attention. Ideally the indications are intuitive, so users adapt to them easily and don't feel oppressed by them. That distinction is in play here. And while I'd love to add a dozen more LEDs, a klaxon horn, and a Van de Graf generator to the K3's user interface, we have to work within the limits of the existing hardware. Providing an optional means of reinforcing split/non-split state is in the tradition of design iteration -- using feedback about real errors that people make, then minimizing them. That's why we're having this conversation. Wayne N6KR ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to li...@subich.com
______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
