[ct-user] F4 key usage

[Robert Naumann]

>From my CT Version 9 manual(1994) page 58:

" If the callsign on the current logging line is a dupe, F4 won't send
anything.
 You can disable this behavior using the WorkDupe text command, and 
 reenable it using NoWorkDupe. "

Sounds like it really was supposed to do this at some point.
It would have been a nifty feature.

73,
Bob Naumann
N5NJ


----------
> From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
> To: David Blaschke <w5un@wt.net>; CT-USER@contesting.com
> Subject: Re: [ct-user] F4 key useage
> Date: Wednesday, November 26, 1997 16:53
> 
> At 04:49 PM 11/26/97 +0000, David Blaschke wrote:
> 
> >I am using CT Ver. 9.?. In my CT manual, on page 58, it tells me that if
I
> >have enabled NoWorkDupe, then, place a duplicate call on the command
line
> >and press F4 to send my call, NOTHING WILL BE SENT. My problem is - MY
CALL
> >IS SENT AS USUAL. Am I overlooking something? or is this a bug in the
> program?
> 
> No, that's not what it is supposed to do.  Say someone calls you and you
> enter the call into CT.  Then you use INSERT to send the call and
exchange.
>  If NOWORKDUPE is set, CT will send the "QSO B4" message instead of the
> contest exchange.
> 
> It changes what the INSERT key does.  F4 ALWAYS send your callsign.
> 
> - Jim AD1C
> 
> --
> Jim Reisert AD1C <jjreisert@alum.mit.edu>     
http://jjr.ne.mediaone.net/
> 
> 
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.contesting.com/ct/
> Questions:                owner-ct-user@contesting.com

--
Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.contesting.com/ct/
Questions:                owner-ct-user@contesting.com