Peter Laws / N5UWY
On Mon, Jul 19, 2021 at 5:10 PM Dave AA6YQ <firstname.lastname@example.org> wrote:
+ The Launcher's Workspaces window displays the Workspaces present in the current Workspaces folder (which defaults to the Launcher's Workspaces folder). If you move a new folder into the current Workspaces folder while the Launcher is running, terminate and restart the Launcher; the new folder should now be present on the Launcher's Workspaces window.
2) Move the DXKeeper MDB with the club log before or after the workspace shenanigans?The whole point of moving the workspace from my PC to the new
trustee's PC is so he can maintain the log for the club station. Do I
not need to bother with the workspace part at all and just Dropbox him
the database? 'Cause that makes the rest of this moot. :-)
c:/apps/DXLab/Launcher/Workspaces contains a number of directories,
one for each workspace as I guess you'd expect. In each of these
directories are files with the name of the various DXL modules. None
of them have .reg extensions (yes, I have "hide extensions" turned off
because that's weird and I'm looking at them in PowerShell in any
case). All appear to *be* Registry entries, e.g.,
[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper]
[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper\ADIF]
et cetera so we're talking about the same items regardless of how they
may be named.
Looking at the club DXKeeper stuff in the club workspace, I see my own LOTW and TQSL credentials in addition to the club's ... what did I doIn the DXKeeper file (no .reg) within the Workspace directory
corresponding to the club's callsign, I find my own callsign in
addition to the club call.
I would like to clean that up in a programmatic way since my
inclination is to go to Windows Subsystem for Linux, and edit the
suckers out of there with vi ... but that's probably not the best way.
Peter Laws | N5UWY | plaws plaws net | Travel by Train!