[wsjt-devel] Fwd: Re: [wsjtgroup] Rig control error - wsjtx v1/4

2014-10-01 Thread ki7mt
Forwarded Message Subject:Re: [wsjtgroup] Rig control error - wsjtx v1/4 Date: Wed, 1 Oct 2014 22:01:56 -0400 From: 'Rudy Benner' r...@vianet.ca [wsjtgroup] Reply-To: Rudy Benner To: wsjt FT450 Hamlib error: Protocol error while getting mode of split

[wsjt-devel] Fwd: [wsjtgroup] Rig control error - wsjtx v1/4

2014-10-01 Thread KI7MT
Original Message Subject:[wsjtgroup] Rig control error - wsjtx v1/4 Date: Wed, 1 Oct 2014 21:26:43 -0400 From: Peter Pauly ppa...@gmail.com [wsjtgroup] Reply-To: Peter Pauly To: wsjt Hamlib error - protocol error while getting split TX VFO. I've tried a

[wsjt-devel] WSJT-X v1.4 branch issue log

2014-10-01 Thread Bill Somerville
Hi All, as I am addressing several issues forthcoming from Beta users, I have checked in a file called "issue log.txt" into the wsjtx-1.4 branch. Feel free to update if you are working on other issues or can add details to current outstanding issues. 73 Bill G4WJS. ---

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Laurie VK3AMA
As I type this, I can see that 83 JTAlert users are running v1.4. There have been no reported errors on the HamApps group. de Laurie, VK3AMA On 2/10/2014 5:48 AM, Bill Somerville wrote: Hopefully a good number of v1.4

Re: [wsjt-devel] Windows 1.40-rc2 Issues

2014-10-01 Thread Bill Somerville
On 02/10/2014 00:36, Josh Rovero wrote: Hi Josh, > I normally run 7 instances of wsjtx simultaneously under W7 64-bit. > Each instance of wsjtx (and fldigi, and 2*hdsdr) runs in a separate > Finestra workspace. > > The new 1.40-rc2 won't "stay" in a Finestra workspace, > and instead insists on bein

[wsjt-devel] Windows 1.40-rc2 Issues

2014-10-01 Thread Josh Rovero
I normally run 7 instances of wsjtx simultaneously under W7 64-bit. Each instance of wsjtx (and fldigi, and 2*hdsdr) runs in a separate Finestra workspace. The new 1.40-rc2 won't "stay" in a Finestra workspace, and instead insists on being "on top" no matter which workspace is selected. This isn'

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
Hi Bill, I have internet issues something chronic at the moment. T-Bird said this email failed to deliver like 5 times, so if you get multiples of it, apologies for that :-) I got your other mail about plugins as well. The next update can take them out if not needed. On 10/1/2014 19:48, Bill Som

Re: [wsjt-devel] V 1.4.0-rc2

2014-10-01 Thread Joe Taylor
Hi Eddy, Thanks for your report. I'm not aware of any problems with v1.4 talking to an FT-847, but we'll look into it and will be in touch if we need more information. -- Joe, K1JT On 10/1/2014 2:26 PM, Edward Payne wrote: > Hi Joe, > > I would like to firstly say that your software h

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Bill Somerville
On 01/10/2014 20:43, KI7MT wrote: > i Joe, Bill, Hi Greg, > > I've updated the jtsdk-cmake.bat file so it *does not copy* files over > to install\Debug\bin, rather, it sets paths to GCC, FFTW, QT5 and Hamlib > Dir's. > > I wasn't sure if we needed hamlib3\minge32\{bin,lib} or not so I added > them

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
i Joe, Bill, I've updated the jtsdk-cmake.bat file so it *does not copy* files over to install\Debug\bin, rather, it sets paths to GCC, FFTW, QT5 and Hamlib Dir's. I wasn't sure if we needed hamlib3\minge32\{bin,lib} or not so I added them nonetheless. If not, we can take that back out. It's ru

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Bill Somerville
On 01/10/2014 19:35, Bill Somerville wrote: > On 01/10/2014 19:18, KI7MT wrote: > >> I've been copying gcc & Qt5 runtime libs over because Qt5 is not in my >> env %PATH% var (by design) otherwise I get Missing Lib errors when running. > OK, I think you need to have the Qt bin directory in your path

[wsjt-devel] Archival releases

2014-10-01 Thread Joe Taylor
It seems that it's probably time to remove the "Archival Windows releases" (v1.1, r3496 and v1.2.1, r3590) from the WSJT web site. Does anyone know of reasons why either should be retained any longer? -- Joe, K1JT -

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
Hi Joe, I took it off the %PATH% string for all 5 files, and was testing all the builds before sending the next update. 73's Greg, KI7MT On 10/1/2014 18:47, Joe Taylor wrote: > RR, 4427 is OK. > > But if LIBRARY_PATH defined to be a NULL string, why include it in PATH > at all? > > -- J

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Joe Taylor
RR, 4427 is OK. But if LIBRARY_PATH defined to be a NULL string, why include it in PATH at all? -- Joe On 10/1/2014 2:40 PM, KI7MT wrote: > Hi Joe, > > Yes, it did here too. Had to move the %LIBRARY_PATH% to the end of the > %PATH% > > Should be ok now, I just built WSPR and WSJT-X > >

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
Hi Bill, On 10/1/2014 18:35, Bill Somerville wrote: >> So for the Debug builds, are you saying we don't need to copy the >> runtime .dll's over too the install\bin directory ? > Yes, that's the way it works for me. > > Yuck! I hate Windows. I've just checked using the dependency walker and >

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
Hi Joe, Yes, it did here too. Had to move the %LIBRARY_PATH% to the end of the %PATH% Should be ok now, I just built WSPR and WSJT-X 73's Greg, KI7MT On 10/1/2014 18:34, Joe Taylor wrote: > Greg -- > > SVN revisions 4425 and 4426 break everything here. > > I think all that's needed is > >

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Joe Taylor
Greg -- SVN revisions 4425 and 4426 break everything here. I think all that's needed is SET LIBRARY_PATH="" in jtsdk-qtenv.bat, and possibly also in jtsdk-pyenv.bat. Don't put LIBRARY_PATH into PATH... they're two different things. You don't use LIBRARY_PATH anywhere in your scripts

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Bill Somerville
On 01/10/2014 19:18, KI7MT wrote: > Hi Bill, Hi Greg, > > On 10/1/2014 18:06, Bill Somerville wrote: >> On 01/10/2014 18:41, Joe Taylor wrote: >> >> Hi Joe, >>> Greg -- >>> >>> I finally spent the necessary time to find out why builds of WSJT-X on >>> one of my shack computers stopped working, a co

Re: [wsjt-devel] [wsjt:wsjt] [r4427] - ki7mt: Move LIBRARY_PATH to end of C:\JTSDK-DOC\doc; C:\JTSDK-DOC\doc\asciidoc; C:\JTSDK-DOC\subversion\bin; C:\JTSDK-DOC\doc\inno5; C:\JTSDK-DOC\tools; C:\JTSDK

2014-10-01 Thread KI7MT
I had an error during the svn update. I think it was because I added %PATH% in the commit line, wont do that again :-). Apologies for that The files look ok though. 73's Greg, KI7MT On 10/1/2014 18:31, Repository WSJT wsjt wrote: > Move LIBRARY_PATH to end of > C:\JTSDK-DOC\doc;C:\JTSDK-DOC\doc\

Re: [wsjt-devel] Fwd: Re: Public beta release of WSJT-X 1.4.0

2014-10-01 Thread Bill Somerville
On 01/10/2014 19:06, Joe Taylor wrote: Hi Joe, > FYI I have sent a request for more information to their email address, hopefully they are watching their yahoo email account. 73 Bill G4WJS. > > Original Message > Subject: Re: Public beta release of WSJT-X 1.4.0 > Date: Wed, 1 O

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
Hi Bill, On 10/1/2014 18:06, Bill Somerville wrote: > On 01/10/2014 18:41, Joe Taylor wrote: > > Hi Joe, >> Greg -- >> >> I finally spent the necessary time to find out why builds of WSJT-X on >> one of my shack computers stopped working, a couple of weeks ago. >> >> Turns out that the machine in

[wsjt-devel] Fwd: Re: Public beta release of WSJT-X 1.4.0

2014-10-01 Thread Joe Taylor
FYI Original Message Subject: Re: Public beta release of WSJT-X 1.4.0 Date: Wed, 1 Oct 2014 11:01:05 -0700 From: pennino...@yahoo.com [wsjtgroup] Reply-To: To: Split operation has a bug; this worked fine in 1.3. TS-2000 with Commander for control. If split is set to rig, it

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Bill Somerville
On 01/10/2014 18:41, Joe Taylor wrote: Hi Joe, > Greg -- > > I finally spent the necessary time to find out why builds of WSJT-X on > one of my shack computers stopped working, a couple of weeks ago. > > Turns out that the machine in question has environment variable > LIBRARY_PATH set as follows,

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread KI7MT
Hi Joe, Setting to null would correct any inadvertent settings of the Path elsewhere I would think. The other question is, how is that getting in there to begin with if the env / build script is not, or should not, be picking up any of the local env variables. Can you add it to jtsdk-qtenv.bat,

[wsjt-devel] LIBRARY_PATH in JTSDK-QT

2014-10-01 Thread Joe Taylor
Greg -- I finally spent the necessary time to find out why builds of WSJT-X on one of my shack computers stopped working, a couple of weeks ago. Turns out that the machine in question has environment variable LIBRARY_PATH set as follows, at login: LIBRARY_PATH=c:\mingw\lib;c:\mingw\lib\gcc-lib

Re: [wsjt-devel] WSJT-X web page.

2014-10-01 Thread Bill Somerville
On 01/10/2014 16:52, Joe Taylor wrote: > Tnx Bill -- I believe they're fixed now. RR, OK now. > > -- Joe 73 Bill G4WJS. > > On 10/1/2014 11:40 AM, Bill Somerville wrote: >> Hi Joe, >> >> links to the 1.4 user guide are broken, pointing to a file on C:. >> >> 73 >> Bill >> G4WJS. ---

Re: [wsjt-devel] WSJT-X web page.

2014-10-01 Thread Joe Taylor
Tnx Bill -- I believe they're fixed now. -- Joe On 10/1/2014 11:40 AM, Bill Somerville wrote: > Hi Joe, > > links to the 1.4 user guide are broken, pointing to a file on C:. > > 73 > Bill > G4WJS. > > -- > Meet PC

[wsjt-devel] WSJT-X web page.

2014-10-01 Thread Bill Somerville
Hi Joe, links to the 1.4 user guide are broken, pointing to a file on C:. 73 Bill G4WJS. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS

[wsjt-devel] Public beta release of WSJT-X 1.4.0

2014-10-01 Thread Joe Taylor
To: Users and potential users of WSJT-X From: K1JT, for the WSJT development team This message is to let you know that a public beta release of WSJT-X, version 1.4.0, is now available. Installation instructions and download links for Windows, Linux, and OS X can be found on the WSJT home page

Re: [wsjt-devel] Double-click causes unnecessary changes of VFO A ?

2014-10-01 Thread Bill Somerville
On 01/10/2014 16:05, Joe Taylor wrote: > Bill -- Hi Joe, > > Yes, TS-2000. I can use either a Debug or Release configuration -- let > me know which would be useful. I probably won't get to doing further > tests until this evening. OK in a Debug configured build tree set the following CMake option

Re: [wsjt-devel] Double-click causes unnecessary changes of VFO A ?

2014-10-01 Thread Joe Taylor
Bill -- Yes, TS-2000. I can use either a Debug or Release configuration -- let me know which would be useful. I probably won't get to doing further tests until this evening. -- Joe On 10/1/2014 10:59 AM, Bill Somerville wrote: > On 01/10/2014 15:56, Joe Taylor wrote: >> Hi Bil

Re: [wsjt-devel] Double-click causes unnecessary changes of VFO A ?

2014-10-01 Thread Bill Somerville
On 01/10/2014 15:56, Joe Taylor wrote: > Hi Bill, Hi Joe, > > I'm using the hamlib interface. OK, that shouldn't happen. I assume that is with a TS-2000. I need to see a trace from that to see exactly what is happening. Do you normally test with a Debug or Release configuration build? > > -

Re: [wsjt-devel] Double-click causes unnecessary changes of VFO A ?

2014-10-01 Thread Joe Taylor
Hi Bill, I'm using the hamlib interface. -- Joe On 10/1/2014 10:24 AM, Bill Somerville wrote: > On 01/10/2014 15:22, Joe Taylor wrote: > Hi Joe, >> I have noticed that when operating in Split mode, double-clicking on a >> line of decoded text causes a momentary change of VFO A frequency,

Re: [wsjt-devel] Double-click causes unnecessary changes of VFO A ?

2014-10-01 Thread Bill Somerville
On 01/10/2014 15:22, Joe Taylor wrote: Hi Joe, > I have noticed that when operating in Split mode, double-clicking on a > line of decoded text causes a momentary change of VFO A frequency, > whenever the final result will also change the frequency of VFO B. > > Yes, at the end VFO A is reset back w

[wsjt-devel] Double-click causes unnecessary changes of VFO A ?

2014-10-01 Thread Joe Taylor
I have noticed that when operating in Split mode, double-clicking on a line of decoded text causes a momentary change of VFO A frequency, whenever the final result will also change the frequency of VFO B. Yes, at the end VFO A is reset back where it should be; but why is it changed, at all? Is