On 26/03/2014 18:41, Greg Beam wrote:
Hi Bill,
Hi Greg,
See questions below:
On 3/26/2014 13:46, Bill Somerville wrote:
One very noticeable change is that the location of ancillary files
have changed. Writeable persistent data files now go to a "well
known" user specific location on each platform:
Windows: %APPDATA%\WSJTX Linux: $HOME/.local/share/wsjtx Mac:
$HOME/Library/Application Support/WSJT-X and
$HOME/Library/Preferences
These locations may vary slightly with o/s version due to file
system layout variations.
Note that you do not need to put any files into these locations,
they get created by the running program itself. Also several files
have been built directly into the wsjtx binary as resources so
don't be worried that there don't appear to be any sample .WAV
files, Palette files or, kvasd.dat in the build or install output
directories.
I don't use this feature much (plenty for me to choose from as it is
:-) ), but there are others that build their own Palettes. How would
they add a custom Palette? Does it need to be added to the source tree
then compiled in for the next release or something?
Yes that probably needs an enhancement to allow direct user palette
creation. I did think of doing it, it's not too difficult to implement
as a directory somewhere (probably in the data directory) where any .pal
files would get merged into the standard ones.
My priority was on getting the standard palettes in a place where their
install location could be properly controlled on all platforms.
Incidentally the cty.dat file is already handled in a similar way, it is
built into the wsjtx binary as a resource but if it is found in the data
directory that copy will be used in preference.
Are you saying the samples are compiled into the wsjtx.exe binary as well?
Yes they are compiled into the wsjtx binary as a resource, but in this
case they are copied out to the default save directory in the 'samples'
directory on program startup (if they aren't there already). Palettes
could also be handled that way which would also be fairly simple.
The consequence of this is two fold:
1) the settings will need redoing, as it happens the changes to
the settings .INI file are so great that a complete reset is best
anyway;
2) on Windows JTAlert will not work because JTAlert reads a couple
data files that WSJT-X writes to get program status. As an
intermediate measure until Laurie VK3AMA accommodates the new file
locations there is a CMake option to revert the location back to
where it is in the current release. This option is
WSJT_STANDARD_FILE_LOCATIONS which is ON by default, turn it off
and build if you want to interoperate with the current version of
JTAlert.
Using a cmake-tool-chain file, can we use that to switch default file
locations, something like:
SET (WSJT_STANDARD_FILE_LOCATIONS OFF)
??
It is a configure option, I'm not sure that belongs in a tool-chain file
since that is supposed to describe the build system rather than the
target or build configuration.
I use cmake-gui to change configuration options in the cmake cache. The
cache is the place where such decisions are supposed to be recorded.
That's all for now, there will surely be many more questions I need
to answer.
73 Bill G4WJS.
73's
Greg, KI7MT
Hope this helps,
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
