Re: [wsjt-devel] Omnirig patch

Change Omnirig to error message instead of segfault when unsupported mode is selected. https://www.dropbox.com/s/cn2pswqihhgec2g/omnirig.patch?dl=1 There may be more problems that are timing based but this solves one at least. de Mike W9MDB-

Re: [wsjt-devel] Error patch

> On Apr 20, 2018, at 5:12 PM, Bill Somerville wrote: > > Good God, I've done it again. Apologies to all. Thank you for admitting to be human, Bill !!! Thanks for all you do, really. Gary - AG0N -- Check out the vib

Re: [wsjt-devel] Error patch

On 21/04/2018 00:10, Bill Somerville wrote: off list - his time correctly. Good God, I've done it again. Apologies to all. 73 Bill G4WJS. -- Check out the vibrant tech community on one of the world's most engaging te

Re: [wsjt-devel] Error patch

On 10/04/2018 13:52, Black Michael via wsjt-devel wrote: When the save directory is messed up the error message isn't quite as useful as it could be. Add the file path to the wav file error message https://www.dropbox.com/s/u3x6xatwgpzapnu/error.patch?dl=1

Re: [wsjt-devel] Feature Request: fold logger Grid Square to upper case

On 16/04/2018 18:04, Gustafson Neil via wsjt-devel wrote: Hello:    First, thank you for the excellent WSJT-X software!    A low-priority feature request:    In logging contacts, it is customary to record Maidenhead Grid in the format AA99 where the first two characters are upper-case alpha.  (

Re: [wsjt-devel] Type 2 compound callsigns support

On 20/04/2018 21:59, g...@isect.com wrote: Hi Bill. /LH is another common lighthouse designation, and I guess a vanishingly rare Norwegian location modifier 73 Gary ZL2iFB Hi Gary, thanks for that, added. No idea how I missed that one. 73 Bill G4WJS. -

Re: [wsjt-devel] Type 2 compound callsigns support

Hi Bill. /LH is another common lighthouse designation, and I guess a vanishingly rare Norwegian location modifier 73 Gary ZL2iFB -Original Message- From: Bill Somerville Sent: Saturday, 21 April 2018 8:36 a.m. To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Type 2 compo

Re: [wsjt-devel] Omnirig patch

On 20/04/2018 21:53, Bill Somerville wrote: On 20/04/2018 21:33, Black Michael via wsjt-devel wrote: Yup...that was the test build version. https://www.dropbox.com/s/muohzuvwcfn96bi/omnirig.patch?dl=1 Mike Hi Mike, off list, that's better. Oops, I didn't check the address, Mike unlike oth

Re: [wsjt-devel] Omnirig patch

I'll try and chase it down from that angle.At this point I know this simply prevents the segfaults that occur.Mike On Friday, April 20, 2018, 3:48:52 PM CDT, Bill Somerville wrote: On 20/04/2018 21:25, Black Michael via wsjt-devel wrote: > Under some condition omnirig settings can c

Re: [wsjt-devel] Omnirig patch

On 20/04/2018 21:33, Black Michael via wsjt-devel wrote: Yup...that was the test build version. https://www.dropbox.com/s/muohzuvwcfn96bi/omnirig.patch?dl=1 Mike Hi Mike, off list, that's better. As a minor aside, in C++ the idiomatic to check if a point is assigned is to simple make use

Re: [wsjt-devel] Omnirig patch

On 20/04/2018 21:25, Black Michael via wsjt-devel wrote: Under some condition omnirig settings can cause a segfault in WSJT-X. This patch prevents some calls from referring to a null rig_ device. Two rigs hooked up.  Change from rig 1 to 2.  Change mode. Restart WSJT-X.  WSJT-X gets a segfault o

Re: [wsjt-devel] Type 2 compound callsigns support

On 14/04/2018 21:48, Alessandro Gorobey via wsjt-devel wrote: Hi Bill, sorry for the intrusion, but I read some public lists with multiple "/". Limiting to https://lotw.arrl.org/lotw-user-activity.csv https://sourceforge.net/p/wsjt/wsjt/8597/tree//branches/wsjtx/cty.dat I found many "/" suff

Re: [wsjt-devel] Omnirig patch

Yup...that was the test build version. https://www.dropbox.com/s/muohzuvwcfn96bi/omnirig.patch?dl=1 Mike On Friday, April 20, 2018, 3:31:13 PM CDT, Bill Somerville wrote: On 20/04/2018 21:25, Black Michael via wsjt-devel wrote: > Change some calls in OmniRigTransceiver to check for ri

Re: [wsjt-devel] Omnirig patch

On 20/04/2018 21:25, Black Michael via wsjt-devel wrote: Change some calls in OmniRigTransceiver to check for rig_ == NULL Under some condition omnirig settings can cause a segfault in WSJT-X. This patch prevents some calls from referring to a null rig_ device. Two rigs hooked up.  Change from r

[wsjt-devel] Omnirig patch

Change some calls in OmniRigTransceiver to check for rig_ == NULL Under some condition omnirig settings can cause a segfault in WSJT-X.This patch prevents some calls from referring to a null rig_ device.Two rigs hooked up.  Change from rig 1 to 2.  Change mode.  Restart WSJT-X.  WSJT-X gets a seg

Re: [wsjt-devel] Possible bug in WSJT-X 1.90 RC3 R8570

Thanks, Bill, Yes, each time. No message box appears, just bouncing dock icon. David, WA1OUI On Apr 20, 2018, at 4:16 PM, Bill Somerville wrote: Hi David, my apologies, I assumed you had one or both of the two check boxes below "Accept UDP requests". As you don't, I am not sure why you ar