K3: too easy to overwrite dial memories

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: K3: too easy to overwrite dial memories

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, 30 May 2008 20:18:03 +0100, David Ferrington, M0XDF wrote:
> 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
order
> for the computer program to best succeed.
> This is no longer the case and I don't accept that any program
is so
> limited that it makes it difficult for the human.
>
> This is what the basis of all modern computing should be. That
goes
> for the K3 too, which by the way I love and am NOT complaining
about,
> but I would prefer some form of confirmation step before I
overwrite a
> memory.
> This does not need to be a sting of 'Are You Sure', 'Are You
Really
> Sure You Want To", 'Are you sure you DONT want too'! - just
something
> like a contiguous two button press or one button twice is
sufficient
> and that should be configurable for those that don't want that
feature.
> </RANT>
>
> 73 de M0XDF, K3 #174


_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
Reply | Threaded
Open this post in threaded view
|

Re: K3: too easy to overwrite dial memories

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 and those that do can use it and we  
can choose which memories it applies to, as we set them.

Now I'd like the feature, but not at the expense of other more  
pressing issues.
73 de M0XDF, K3 #174
--
If you must play, decide on three things at the start: the rules of the
game, the stakes, and the quitting time. -Chinese Proverb

On 31 May 2008, at 08:15, Stewart Baker wrote:

> 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.

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
Reply | Threaded
Open this post in threaded view
|

Re: K3: too easy to overwrite dial memories

Leigh L. Klotz Jr WA5ZNU
Administrator
In reply to this post by KENT TRIMBLE
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 the software for the front panel UI.  Channelized tuning (for
example, for 60m or for mobile) was something that was said to be on the
list for a future version.  It's not the most important area to attend
to right now (that's probably the 2ND RX) but it should get done.  And
when it does, some kind of look at the whole channel/memory/tuning thing
is called for.

By the way, I also own a KX1 and a K2, and have spent considerably time
with a K1 as well.  

73 es TNX,
Leigh/WA5ZNU

> 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 months since, I have not overwritten anything.
>
> As has been said for a full year now, the K3 is a complicated piece of
> gear.  At least initially.  A complicated radio requires understanding
> and effort on the owner's part.  If you wish not to exert the required
> effort (no shame in that), there are several good entry-level rigs out
> there by competent manufacturers, both foreign and domestic.  But
> there is no reason to demand reinvention of the front panel and
> associated circuitry merely because you find certain features awkward
> at first.
>
>
> K9ZTV
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
> http://mailman.qth.net/mailman/listinfo/elecraft   
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
12