Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-31 Thread Stewart Baker
Likewise, I don't want Are you sure ? messages. What would suit me would be a few scratch memories that are unprotected. Maybe a setting under the VFOB Menu display which could switched from Protect/Unprotect for the other memories that I had spent some time setting up. 73 Stewart G3RXQ On Fri,

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-31 Thread David Ferrington, M0XDF
That sounds like the best option so far Stewart, allow us to mark a memory as read-only in some way as we save it and then to overwrite it, you have to flip the switch to write-enable. Default all memories to write-enable and that way all those who don't want this feature just ignore it

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-31 Thread Leigh L. Klotz, Jr.
Kent, There's a balance between asking for design changes and carping and it's sometimes hard to know where to draw the line... Note my original message just stated the problem I had without stating a possible solution... I'll leave that to Elecraft, as they are still actively developing

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-30 Thread K9ZTV
Guys . . . This is much ado about nothing. Just LEARN how the K3 does memory storage and retrieval and it will become second-nature to you. During the first week or two following assembly I overwrote some memories a time or two myself . . . until I trained myself not to. In the nine

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-30 Thread Ian J Maude
K9ZTV wrote: Guys . . . This is much ado about nothing. Just LEARN how the K3 does memory storage and retrieval and it will become second-nature to you. During the first week or two following assembly I overwrote some memories a time or two myself . . . until I trained myself not to. In

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-30 Thread hank k8dd
- Original Message From: Ian J Maude [EMAIL PROTECTED] K9ZTV wrote: Guys . . . This is much ado about nothing. Just LEARN how the K3 does memory storage and retrieval and it will become second-nature to you. With respect Kent, (and I know your email was

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-30 Thread David Ferrington, M0XDF
At the risk of offending someone - computers (and the K3 has a certain amount of that) should be programmed to serve humanity and not the other way around. I've been in IT 39 years and there was a time when I accepted that a human might have to work a certain way or act a certain way in

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Ian J Maude
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

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread 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

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Stewart Baker
Although there are some young people coming into the hobby, a large proportion (myself included) are of the more senior variety. I find that it is far too easy when it comes to using the K3 memories to press the wrong button, and overwrite something one wanted to keep. This action is normally

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Ken K3IU
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

Re: Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread d.cutter
Thinking about the old tape recorders: it was made harder to over-record an existing recording by having to press 2 buttons at once. Is this possible? David G3UNA - Email sent from www.virginmedia.com/email Virus-checked using McAfee(R) Software and

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread David Ferrington, M0XDF
might be worthwhile keeping some memories that don't require that - I keep 00 to 09 for storing some frequency i want to come back to shortly - I'm not using M1-M4 for that since I store various frequency in them for the band - like start of band, start of SSB, end of SSB etc more

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Joe Planisky
How about a single level 'undo' or 'Recycle Bin' that saves the last modified memory contents. That way, if you realize you've overwritten a memory by mistake, you can 'undo' to get the original contents back. 73 -- Joe KB8AP On May 29, 2008, at 5:17 AM, David Ferrington, M0XDF wrote:

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread David Ferrington, M0XDF
that is a very good idea -- There is a coherent plan in the universe, though I don't know what it is a plan for. - Fred Hoyle On 29 May 2008, at 13:51, Joe Planisky wrote: How about a single level 'undo' or 'Recycle Bin' that saves the last

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Eric Scace K3NA
In the world of ergonomics and man-machine interface design, there is a rule: If an action will destroy information or a state than cannot be restored with the same effort that it took to destroy, then the system requires either (a) a Un-Do function of equal simplicity, or (b) a

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread G4ILO
Eric Scace K3NA wrote: In the world of ergonomics and man-machine interface design, there is a rule: If an action will destroy information or a state than cannot be restored with the same effort that it took to destroy, then the system requires either (a) a Un-Do function of equal

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread David Cutter
Would your rule be covered if you had to hold in another button at the same time as hitting the memory button? Or, say, turn the power to zero before making memory additions... David G3UNA In the world of ergonomics and man-machine interface design, there is a rule: If an action will

RE: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Ed Lambert
For example, a (hypothetical!) button that shuts down the jet engines on an aircraft requires a confirmation step... because turning off the engines until the pilot hits UnDo would be bad! This rule applies to software as well as hardware. -- Eric K3NA This has no bearing on the

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread Dr. Werner Furlan
Phil, Phil Debbie Salas schrieb am 29 May 2008 um 10:57: Or maybe just require two presses of VM? That's the way one of my talkies works. When I hit VM, the memory number flashes. Hitting VM again stores the info in that memory. I find this a very good proposal. 73! de Werner OE9FWV

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread David Ferrington, M0XDF
no way do it want to drop power to zero, just so i can load a memory -- The trees that are slow to grow bear the best fruit. -Moliere, actor and playwright (1622-1673) On 29 May 2008, at 17:49, David Cutter wrote: Would your rule be covered if you had to hold in another button at the same

Re: [Elecraft] K3: too easy to overwrite dial memories

2008-05-29 Thread hank k8dd
And then it would be nice to hear the memory when you press MVFO as you step through the memories. 73HankK8DD -- 'Never argue with an idiot. They drag you down to their level then beat you with experience.' -anon -- Phil Debbie Salas schrieb am 29 May 2008 um 10:57: Or maybe