[WT-support] Disabling Cut Number Translation on Receive

Colin colin at g3psm.net
Wed Feb 17 12:51:54 CET 2010


Ah, that's what was happening.   Sometimes I need to think laterally!

73

Colin, G3PSM

Bob Wilson, N6TV wrote:
> As one of the people who originally supported the idea of cut number 
> translation when entering QSO numbers, I have since realized that the 
> implementation of this suggestion has caused far more problems than I 
> ever anticipated.  Instead of Win-Test trying to handle it on a 
> case-by case basis, contest-by-contest, I think there should just be 
> one new global option:  Tools | Data Entry | Translate cut numbers 
> (keyboard shortcuts: CUTON / CUTOFF).  That way you can leave it OFF 
> most of the time but easily enable it whenever it is needed. 
>
> Obviously this option should only affect what happens when you press 
> [Enter] or [+]; it should not change anything entered on other QSOs.
>
> 73,
> Bob, N6TV
>
> On Tue, Feb 16, 2010 at 5:21 AM, Andy Cook, G4PIQ 
> <g4piq at btinternet.com <mailto:g4piq at btinternet.com>> wrote:
>
>     I was operating in the RSGB 1.8 MHz contest this weekend. Exchange
>     for that contest is RST + Serial + UK District Code. However, at
>     the same time the PACC contest was running where entrants sent RST
>     + Dutch Region Code. Win-Test allowed me to log Dutch regions into
>     the serial number field OK (I didn't want log 000 as a serial and
>     enter the Dutch Regions into the UK District Code column in order
>     to avoid issues with multiplier count where UK and Dutch codes
>     overlapped), but the automatic correction of cut numbers meant I
>     had to do a pile of cleaning up post-contest.
>      
>     e.g. NH would end up logged as 9H and UT would end up logged as 020!
>      
>     I can see the options to stop sending / configure what you send
>     for cut numbers, but I can't see an option to turn off cut-number
>     translation on receive.
>      
>     I was running v4.4.0. What seems even stranged is that G3BJ was
>     doing the same thing (running v4.4) and had no problem.
>      
>     What have I missed!
>      
>     73,
>      
>     Andy, G4PIQ
>
>     _______________________________________________
>     Support mailing list
>     Support at win-test.com <mailto:Support at win-test.com>
>     http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>   


More information about the Support mailing list