After unchecking that box, JTAlert is now working fine for me. On Wed, Sep 26, 2018 at 8:24 PM <kd2...@gmail.com> wrote:
> You may run into bugs that were fixed from RC1 to RC2 (like the issue with > some callsigns being translated as telemetry and subsequent program crashes > as a result). That may end up being frustrating to you and to your QSO > partner. > > Jim S. > N2ADV > > -----Original Message----- > From: Don Hill AA5AU [mailto:aa...@bellsouth.net] > Sent: Wednesday, September 26, 2018 6:29 PM > To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net> > Subject: [wsjt-devel] -rc1 or -rc2 for FT8 RU tonight? > > I saw Joe's post that says we can use either rc1 or rc2 in tonight's FT8 RU > test. I have not upgraded to -rc2 yet because of the JTAlert bug since > JTAlert is extremely important to me right now. > > What will be detrimental to running -rc1 instead of -rc2 in tonight's test? > > I am willing to upgrade to -rc2 before the test if someone can confirm that > all I need to do to get JTAlert to work properly is to un-check "Show DXCC, > grid, and worked-before status" on the General tab of WSJT-X Settings? > > I would prefer to run -rc2 for the test tonight. > > Thanks, > Don AA5AU > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
