And when you are installing WSJT-X can you show how you install it?
Mike W9MDB
On Saturday, June 6, 2020, 10:53:26 PM CDT, Topher Petty <[email protected]>
wrote:
Apparently the statically linked WSJT-X with its own hamlib does...Neither
FLDIGI nor the SKCClogger does these things on startup..As SKCClogger is
written in Python and references my local copy of hamlib, this shows that
hamlib most likely isn't the issue.But you're right... I should contact the
hamlib team about symptoms that only appear when I use a software that is
statically linked to hamlib and is the only place where the symptoms occur.
On Sat, Jun 6, 2020, 20:17 Bill Somerville <[email protected]> wrote:
On 07/06/2020 01:08, Topher Petty wrote:
> For example:
> I won't report that, for some reason, 2.2.1 seems to cycle my 7300
> from VFO A to VFO B and back to VFO A on startup, which makes me need
> to press the "TUNE" button again to get the auto-tuner back in sync
> with the radio. I won't report that changing bands to a band 15m and
> above using the dropdown in WJST-X automatically turns my preamp on..
> sometimes it's Preamp1, others Preamp2, and sometimes not at all.
> I also won't report that both of these behaviors are undesirable.
> de AI8W
Chris,
I suggest you report all those issues to the Hamlib team, WSJT-X doesn't
do any of that.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
