[Elecraft] K3: too easy to overwrite dial memories

[David Ferrington, M0XDF]

I think people are saying it's to easy to tap the wrong button?
I for one have done this a couple of times.
I've also been in cONFIG and then held PF2 - wishing to use the  
function on it and of course overwritten the function with whichever  
CONFIG option I'm on at the time.

It's my fault of course, just finger hassle, but it happens - perhaps  
a confirmation press, like needing to press AFX to confirm?
-- 
The rung of a ladder was never meant to rest upon, but only to hold a  
man's
foot long enough to enable him to put the other somewhat higher.
-Thomas Henry Huxley, biologist and writer (1825-1995)

On 29 May 2008, at 09:52, Ken K3IU wrote:

> I guess I don't understand and so far I only use the memories for  
> "bandswitching." Isn't tapping "V->M" *supposed* to write whatever  
> is in the VFO to whatever memory is selected." What am I missing???
> 73,
> Ken K3IU
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Ian J Maude wrote:
>> Leigh L. Klotz, Jr. wrote:
>>> For about the 3rd or 4th time I've tapped V->M, selected a memory  
>>> (on of the 60m spot frequencies, the only global memories I have),  
>>> rotated the VFO dial, and then tapped V->M again and overwrote the  
>>> memory with the current VFO setting.
>>> Once the 2nd RX gets out it would be nice to get some attention  
>>> paid to the memories; channel mode, especially for 60m but  
>>> probably also for general use (think mobile ops; another K3 owner  
>>> has suggested the VFO B knob for this.), making it harder to  
>>> overwrite, etc.
>> I *totally* agree Leigh!  My brain gets mixed up between the two  
>> and this started to frustrate me so much that I have stopped using  
>> the memories.  I had set up to use band switching this way and for  
>> channel hopping on 60m but I kept overwriting them.  Please can we  
>> have a more robust way of protecting the memories?
>>