[WT-support] Problem with zone guessing in 3.16

[I4UFH HRS]

Not really a fast solution in the middle of a 200 q/h .... HI !!

Fabio I4UFH
  ----- Original Message ----- 
  From: Bob Wilson, N6TV 
  To: support at win-test.com 
  Sent: Tuesday, October 30, 2007 10:30 PM
  Subject: Re: [WT-support] Problem with zone guessing in 3.16


  I had the same problem with WT 3.16.  But after you enter the full call, if you move over to the zone field and press Ctrl-W or Ctrl-K to clear it, then press the space bar a couple times, WT will usually fill in the correct zone. 

  73,
  Bob, N6TV


  On 10/30/07, 4O3A <yt6a at cg.yu> wrote:
    I had the same problems as Tonno. It was very frustrating to know that you have to type correct zone almost on every W's and UAs.

    73
    Ranko
      ----- Original Message ----- 
      From: Tõnno Vähk 
      To: support at win-test.com 
      Sent: Tuesday, October 30, 2007 10:12 PM
      Subject: [WT-support] Problem with zone guessing in 3.16


      I was using the previous version of WT in CQWW as I read about some potential problems with SO2R devices and 3.17 did not list anything important for me as updates.



      So it turned out to be a big mistake as I found out. I checked now and at least in all my computers the zone guessing did not work correctly (it does with latest 3.17.0 version though).



      In my case when exchange guessing set to automatical the exchange was guessed just once based on the first entry to the callsign field andwas never updated any more.



      That means when I entered UA it guessed 16 and even if next digit was 9 it was set to 16 for ever.



      When I entered K then it was set to 05 and K7 did not change it.



      When I entered AA as copied suffix it was set to 05 and entering DL2 in front of it later changed nothing. So I had to manually try to change all those incorrect ones but my log is completely flooded with bogus zones now and I guess I have to manually edit them all. Is there a better way??



      Was this problem due to my wrong settings somehow or others had it as well who used 3.16? I guess it was bug as 3.17 is OK (meaning it is constantly updating the exchange when you change the callsign). And I hope this would never be repeated in any future versions. 



      BTW, when I pressed F11 just once at any time then the exchange guessing always started to work for any given QSO but was broken again for next one. It also works for the first QSO entered - so when you try to reproduce it enter oneQSO and then try next!



      Other than that huge problem everything else worked great and I really liked the S&P options for the other radio to wipe out the callsign field and enter the call to bandmap automatically (not "automagically" though as the dialogue box says:))



      73

      tonno

      es5tv







--------------------------------------------------------------------------


      _______________________________________________
      Support mailing list
      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






------------------------------------------------------------------------------


  _______________________________________________
  Support mailing list
  Support at win-test.com
  http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20071030/08a105d3/attachment-0001.htm