Re: [wsjt-devel] Interesting feature. Bug can be reproduced

It might be so. But testing a program is to find all possible odd cases users may create (you'll never complete that !) and find fixes for them. This case upcase shift should be done just before message is prepared for transmit, always. Or prevent typing with low case to edit boxes (run upcase

Re: [wsjt-devel] Bug when responding to K3ZK CQ

Thanks for the feedback Bill ! I appreciate it.   73 Phil, F5FDV   Envoyé: dimanche 23 décembre 2018 à 19:04 De: "Bill Somerville" À: wsjt-devel@lists.sourceforge.net Objet: Re: [wsjt-devel] Bug when responding to K3ZK CQ On 23/12/2018 16:16, t...@gmx.fr wrote: > Something strange happened

Re: [wsjt-devel] bug in 77-bit message packing

On 24/12/2018 02:34, Bill Somerville wrote: The change is attached as a diff for your review. Hi Igor, that patch has a defect, the attached needs to be applied as well to fix that. 73 Bill G4WJS. commit de9990bb60f3cefcefa5a994ade9fa60d3a1d2a4 Author: Bill Somerville Date: Mon Dec 24 0

Re: [wsjt-devel] bug in 77-bit message packing

On 22/12/2018 18:45, Joe Taylor wrote: i3.n3 Err Message to be encoded Decoded message  1.   *   DU6/VA3AAA K9ABC RRR  VA3AAA K9ABC RRR  2.   *   DU6/PA3AAA K9ABC RRR   

[wsjt-devel] Mobile operation

Is there a way to have the program automatically update your grid square based on input from a GPS? Second can I use a GPS for the clock updates? I am thinking of operating in many grid squares throughout my travels Chris KI1P Get Outlook for iOS __

Re: [wsjt-devel] Interesting feature. Bug can be reproduced

All you need to do is to TAB or CLICK ANYWHERE outside the TX6 dialog box and they will change to Upper Case during the Enable Tx cycle. The same thing happens if you enter lower case in the DX Call or DX Grid boxes. However, Tx5 does automatically take lower case keystrokes and enter as upper cas

Re: [wsjt-devel] Interesting feature. Bug can be reproduced

Tested this again with rigctld -r 1 (dummy) 1)   Start wsjt-x 2)   Place cursor to TX6 edit box between CQ and YOURCALL 3)   Write 2 letters with low case (e.x.  na) 4)   Enable TX 5)   When TX fires, letters will change to upcase (ex. NA). That is ok. 6)   During TX period, or during following R

Re: [wsjt-devel] wsjt-devel Digest, Vol 58, Issue 306

Good afternoon all, A rather simplistic solution might be to have your location (by callsign) identified in the city.dat file as "CHECK THE GRID". This would work for anyone that is roving (whether in the local geographical area, or across the Pacific). 73, Rick NM3G ... It was funny --

Re: [wsjt-devel] grid square & nonstandard callsign

Jim, Our calls are valid anywhere worldwide ... but I understand your point. Respectfully - a K9 or any standard CONUS amateur call is rather vanilla.  Probably wisely so, the FCC does not require "call by call area" any longer as you well know.  With our mobile society ... we all have heard a ho

Re: [wsjt-devel] grid square & nonstandard callsign

Roger - understand Gary.  But what are the other viable work-arounds or fixes.  After all, not a big issue with versions 1.8.* and 1.9.*?     Danny    W4/AH6FX On Friday, December 21, 2018 2:05 PM, Gary McDuffie wrote: > On Dec 21, 2018, at 09:44, DX Jami via wsjt-devel > wrot

Re: [wsjt-devel] grid square & nonstandard callsign

Bill & Others, Thanks very much for yourresponses.  Too bad AD1C’s CTY.DAT fixwill not work since I go back and forth to Hawaii.  Shucks – nothing is simple these days.  Please keep in mind I am not the only personwith this problem.  Just wait until theDXpedition and DX-vacation season picks up

Re: [wsjt-devel] Bug when responding to K3ZK CQ

On 23/12/2018 16:16, t...@gmx.fr wrote: Something strange happened when I tried reply to a K3ZK's CQ. As usual, I double clicked on the CQ messsage to set up the QSO information. In the "Gen msg" window the sequence ZS1/F5FDV appeared as expected but, when I turned "Enable Tx" on, the sequence

Re: [wsjt-devel] ADI file scanning

On 23/12/2018 14:10, Thomas Kocourek wrote: Thank you Bill. I am staying away from Yahoo Groups. My apologies for using the developer list. Hi Thomas, no apologies necessary for posting issues with WSJT-X here. I was just pointing that the issue and that it was a known defect had been discus

[wsjt-devel] Interesting feature

While keeping cursor at TX6 box (before my call) I did change directed cq between JA and AS. All went ok if I had CAPS on (shift pressed). Few times I missed shift and wrote "ja" instead of "JA". Results can be seen below. Typing "as" or "AS" did not make any difference. When I started to t

Re: [wsjt-devel] ADI file scanning

Thank you Bill. I am staying away from Yahoo Groups. My apologies for using the developer list. On Sun, Dec 23, 2018 at 7:22 AM Bill Somerville wrote: > On 23/12/2018 12:11, Thomas Kocourek wrote: > > I noticed a new error after upgrading wsjt-x to the 2.0 GA version. I > > was getting an invali

Re: [wsjt-devel] ADI file scanning

On 23/12/2018 12:11, Thomas Kocourek wrote: I noticed a new error after upgrading wsjt-x to the 2.0 GA version. I was getting an invalid ADIF file error window pop up. However, there was no additional information. So, I inspected my wsjtx_log.adi file and could not see anything obviously wron

[wsjt-devel] ADI file scanning

I noticed a new error after upgrading wsjt-x to the 2.0 GA version. I was getting an invalid ADIF file error window pop up. However, there was no additional information. So, I inspected my wsjtx_log.adi file and could not see anything obviously wrong. As a last resort, I deleted the blank lines wh