Is that also true for cty.dat, shortcuts.txt and mouse_commands.txt?
I don't see those either and looks like they should be in the exe directory
if I understand the QFile paths correctly.
Mike
From: Bill Somerville [mailto:[email protected]]
Sent: Sunday, March 15, 2015 8:26 AM
To: [email protected]
Subject: Re: [wsjt-devel] CALL3.TXT
On 15/03/2015 13:15, Michael Black wrote:
Hi Mike,
It would appear that's only true on Joe's computer - from wsjtx.iss
WSJT-X will create a CALL3.TXT if none if present. It is a user file and it
is up to the user to populate it by using the "Add" button on the main
screen.
We do not attempt to provide a directory of grid squares for HF usage. It
makes more sense for EME usage because the list of potential calls is much
more stable and finite. We have considered removing the CALL3.TXT feature
from WSJT-X but given that Joe is busy adding VHF and up "slow" modes to it
that is probably a bad idea.
That wsjtx.iss is not used for official release packages, CMake/CPack
deploys only the files installed by CMake. It does this in a platform
independent fashion so we get the same contents everywhere.
Mike W9MDB
73
Bill
G4WJS.
[Files]
Source: "c:\Users\joe\wsjt\wsjtx_install\wsjtx.exe";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx_install\jt9.exe";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx_install\jt9code.exe";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx_install\kvasd.exe";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx_install\*.dll";
DestDir: "{app}";
Source: "c:\Users\joe\wsjt\wsjtx\cty.dat"; DestDir:
"{app}";
Source: "c:\Users\joe\wsjt\wsjtx\kvasd.dat"; DestDir:
"{app}";
Source: "c:\Users\joe\wsjt\wsjtx\wsjt.ico"; DestDir:
"{app}";
Source: "c:\Users\joe\wsjt\wsjtx\qt.conf"; DestDir:
"{app}";
Source: "c:\Users\joe\wsjt\wsjtx\CALL3.TXT";
DestDir: "{app}"; Flags: onlyifdoesntexist
Source: "c:\Users\joe\wsjt\wsjtx\shortcuts.txt";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx\mouse_commands.txt";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx\prefixes.txt";
DestDir: "{app}"
Source: "c:\Users\joe\wsjt\wsjtx_install\save\Samples\130418_1742.wav";
DestDir: "{app}\save\Samples";
Source: "c:\Users\joe\wsjt\wsjtx_install\save\Samples\130610_2343.wav";
DestDir: "{app}\save\Samples";
Source: "c:\Users\joe\wsjt\wsjtx_install\platforms\qwindows.dll";
DestDir: "{app}\platforms";
Source: "c:\Users\joe\wsjt\wsjtx_install\Palettes\*.pal";
DestDir: "{app}\Palettes";
From: Alessandro Gorobey [mailto:[email protected]]
Sent: Sunday, March 15, 2015 3:43 AM
To: [email protected]
Subject: Re: [wsjt-devel] CALL3.TXT
Hi Mike,
CALL3.TXT is generated by wsjtx.
It is initially empty.
It is managed by the group of controls under frequency
Add --> add entry
Lookup --> search and if found calculate azimuth and distance
I comes from WSJT, see:
http://sourceforge.net/p/wsjt/wsjt/HEAD/tree/trunk/CALL3.TXT
BUGS:
If you press lookup and dxcall is empty "DX Grid" is filled with data in the
first line of CALL3.TXT.
Sandro IW3RAB
Il 15/03/2015 06:16, Michael Black ha scritto:
I see there's an attempt to lookup grids if needed from call3.txt but no
such file seems to be included.
I assume it's the same CALL3.TXT that comes from HRD?
Is this an oversight or dead code?
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
