toggle quoted messageShow quoted text
Whoops...I was using JTDX 2.0.1 rc133_2. Sorry!
On Saturday, March 9, 2019, 9:20:33 AM EST, Ed Wilson via Groups.Io <ed.wilson@...> wrote:
I experienced a similar problem when using JTDX 2.0.2 rc133_2...went back to JTAlert 2.12.10 and things seem to be working fine.
On Saturday, March 9, 2019, 9:13:00 AM EST, Bob Davet <davet354tfd@...> wrote:
Weird issue here.
I upgraded today. Using JTDX and JTAlertX. Everything was seemingly working fine. Click on a call sign in JTAlertX and it triggered JTDX. Logged fine. Then clicked on a call sign and it triggered JTDX. The call sign did not come back to me right away so JTDX kept calling. The call sign went into a QSO with another call. JTDX kicked the Enable TX out which it should. I waited for him or any other call sign to click on. Could not get JTAlertX to activate JTDX anymore. I could click on the callsign in JTDX and it functioned fine. JTAlertX was still showing call signs as it should but I couldnt get it to activate JTDX.
I closed JTDX and JTAlertX. Restarted them. That seemed to clear the problem or so I thought. Same issue started up again with another contact.
So I closed the programs again. Restarted them. Problem remained from the beginning this time.
Restarted the computer. Everything cleared and worked. Then it happened again.
Closed program and restarted. Cleared the problem. A little while later it was back.
Reinstalled JTAlertX 2.12.10.
So far that problem has not reappeared.
I don't even know where to start to figure this one out. Very random.