Date   

locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Jim - N4ST
 

The link was provided on this forum yesterday.
Here is a cut 'n paste of Laurie's posting.

_________
73,
Jim - N4ST

___________________________________________________________________
Try this latest build. It may help or it may not.
Please let me know your results.

https://dnl.HamApps.com/Beta/JTAlert.2.16.5.build.0002.Beta.Setup.exe

de Laurie VK3AMA
____________________________________________________________________

-----Original Message-----
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Bobby Chandler
Sent: Monday, May 18, 2020 06:05
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Laurie, I reported this a while ago, but not lately since it is so
intermittent here, but am still having the problem. I would like to try
the new build, if possible.

Bobby/N4AU

--
Bobby Chandler
bobbye@bellsouth.net
n4au@arrl.net


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Bobby Chandler
 

Laurie, I reported this a while ago, but not lately since it is so intermittent here, but am still having the problem. I would like to try the new build, if possible.

Bobby/N4AU

--
Bobby Chandler
bobbye@bellsouth.net
n4au@arrl.net


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Botz Care
 
Edited

I have the same issue. Both on the 32 and 64 bit version.

This morning I reinstalled again (64 bit) and after first test it took 7 minutes till it didn’t showed the callsigns anymore in Jtalert 2.16.5.

Second time after restarting it all it took much longer, about 40 minutes or so.

Hope you can send me the fix too Laurie so I can test that out.

 

Thanks in advance,

Ivan , PD0AI

 
---
Report to Laurie:

Just been testing the new beta 4 hours none stop with WSJTX 2.2.0 RC1.
So far all seems okay to me now. All callsigns still being refreshed every cycle.
Logging to QRZ eQSL HRDLOG also no hickups.

Thanks alot for the fix :)

73,
Ivan PD0AI


locked Duplicate Alt-S Key

Stewart Wilkinson
 

I have noticed that in JTAlert 2.16.5 Alt-S has two functions - it toggles the 'out-of-shack' it high-lights the 'Settings' menu.

I would suggest changing one of these and make sure that there are no other duplicated alt key mapings caused by having the Menu bar.


locked Re: False Keywords Alert

Uwe, DG2YCB
 

Yes, Neal. It is the only alert with this color. After I disabled Keywords Alert it was gone immediately. Must be a bug in JTAlert.
73 de Uwe, DG2YCB


locked Re: Decoded calls colour

neil_zampella
 

If they're grey, possibly you worked them before ??

Neil, KN3ILZ

 

On Sun, May 17, 2020 at 02:27 PM, Tony Dixon G4CJC wrote:

I'm finding the decoded calls in the boxes not easy to read. They look grey and lack distinction. Is there any way to alter the font/colour?
Cheers
Tony G4CJC


locked Bug Report Cleared on My End

Jim Brown
 

Laurie,
On the WSJT reflector, I told you about issues I was having with 2.15.5 and the WSJT-X rc1. Turns out that after a cold reboot of Win10Pro, the problem is gone.  The problem was that after prompting to DXKeeper, the logging would fail and after one or two cycles, decodes would not display in JTAlert. I would re-start JTA decodes would display.

In the last few days, I've spent a lot of time with FT8 on 60M, 30M, and 6M, and the issue is gone.

73, Jim K9YC


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

Jim - N4ST
 

Just got hold of the beta an hour ago.

First glance, it is an improvement.

Definitely runs longer than the current non-Beta version.

When I change WSJT-X configurations, such as FT8 to FT4, JTAlert stops reporting decodes.  But, it is not hard frozen like before. 

The band activity still displays and the pop-up works.

Can still open settings and when moving WSJT-X window, JTAlert remains docked. 

Just no decode reporting.

Exiting and restarting JTAlert restores proper operation with the new WSJT-X configuration.

Not ideal, but it is at least usable again.

 

________________

73,

Jim – N4ST

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Sunday, May 17, 2020 20:07
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

 

On 18/05/2020 7:32 am, John, DK9JC / AK9JC wrote:

Please allow us some more hours of testing. So far I could not reproduce the bug on the beta. Looking very promising yet.

Will keep you posted. TU for the quick fix.

John,

This message thread wasn't target at you as you had just reported the defect. The message was targeted at those who have had access to the new Beta for several days now without a word of feedback!

Tnx for reporting that the Beta is working for you.

de Laurie VK3AMA


locked Re: Alert 2.16.5 not showing country

Chip Harleman
 

I do not see “Extended Display Setting” on the 2.16.5 I just downloaded.  Gone back and forth.  The .4 is working OK.

 

W6TWH


locked Re: Decodes window (F9) Off-On

Bob WB2NVR
 

Me too!  Thanks for the suggestion, Iain.  I moved those files to an Obsolete directory (I hate to delete anything!), and now the Decodes window is working FB.

73 ES GUD DX,

Bob WB2NVR


locked Re: Alert 2.16.5 not showing country

Chip Harleman
 

Appreciate your reply.  Hard to visualize with a two line display.  I like the .4 release, but guess I will give it a try and see how it looks.  Thanks for the input.  This is put to bed.


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

HamApps Support (VK3AMA)
 

On 18/05/2020 7:32 am, John, DK9JC / AK9JC wrote:

Please allow us some more hours of testing. So far I could not reproduce the bug on the beta. Looking very promising yet.

Will keep you posted. TU for the quick fix.

John,

This message thread wasn't target at you as you had just reported the defect. The message was targeted at those who have had access to the new Beta for several days now without a word of feedback!

Tnx for reporting that the Beta is working for you.

de Laurie VK3AMA


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

John, DK9JC / AK9JC
 

40 QSO in the last 2h and no crash. Seems fixed I would say.
Great work!


locked Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

John, DK9JC / AK9JC
 

Please allow us some more hours of testing. So far I could not reproduce the bug on the beta. Looking very promising yet.

Will keep you posted. TU for the quick fix.


locked Regarding JTAlert 2.16.5 randomly stopping display of Callsigns

HamApps Support (VK3AMA)
 

This random stopping of Callsigns display has a potential fix. The fix has been sent directly to all those who have reported the behavior either in this group or in a Support Request.

Those direct email contains a simple message and request...
Try this latest build. It may help or it may not.
Please let me know your results.

Of the 15 people sent the new build link only 2 have responded. Several where sent followup emails requesting feedback with only one response bringing the total response to 3 out of 15.

At this time, with this level of feedback (lack of), I am not willing to make this build a public release. I am not confident the changes made offer a complete fix to this problem.

Come on guys, if the problem is severe enough to post a message, how hard can it be to send a single line email saying the new beta build works or it doesn't. Silence doesn't answer that fundamental question.

FWIW, none of the 30+ JTAlert Test team have experience this problem, so I am relying on those who have to provide some feedback.

de Laurie VK3AMA


locked Re: Decodes window (F9) Off-On

iain macdonnell - N6ML
 


The Decodes window stopped working for me recently too. I'm not sure exactly when. The window would open, but seemed it was not getting populated with new decodes. There were some old records that I was unable to delete. I seem to have resolved this by nuking the decodes database (sqlite file) and allowing a new one to be created. It's working so-far. The file I deleted is decodes.sqlite, which I found in %LOCALAPPDATA%\HamApps\JTAlert\N6ML\Decode . I also deleted a ".bak" and a ".tmp" copy. This was done while JTAlert was not running.

YMMV.

73,

    ~iain / N6ML


locked Re: Losing connection to 2.2.0-rc1

John, DK9JC / AK9JC
 

Same problem here.

64-bit version, no admin privileges on JTalert.
Logging into LogOM 2.6.1.0 does then stop also.
After restart of JTalert it works some time but then suddenly crashes again.

OS: Win 10 pro 1909 latest fixes.


locked Re: One of many Great JTA Features: Right Click "Open Browser to QRZ.com Callsign page"

Michael Black
 

On Sunday, May 17, 2020, 02:38:13 PM CDT, Mark W2OR via groups.io <reston2010mm-orders@...> wrote:


Do the math.
One person, closing one tab, 15 times a day, 300 days a year, times number of years left in that person's life, times number of persons doing this worldwide with this beautiful app, and that's just for one tab of many.


locked Re: Enable Transmit if "CQ only" is checked

Michael Black
 

That's correct -- if they are not calling CQ WSJT-X will not enable transmit -- you have to click Enable yourself.
Very deliberate to prevent auto QSO and highly unlikely to change.
It's not JTAlert doing it...it's WSJT-X.

de MIke W9MDB




On Sunday, May 17, 2020, 03:22:46 PM CDT, gary.sewell@... <gary.sewell@...> wrote:


Negative, I just tried it. If i have "CQ only" turned on and I Click/Double click on a call in JTAlert that is not sending CQ, nothing happens in WSJT-X.


locked Re: Enable Transmit if "CQ only" is checked

gary.sewell@...
 

Negative, I just tried it. If i have "CQ only" turned on and I Click/Double click on a call in JTAlert that is not sending CQ, nothing happens in WSJT-X.

7301 - 7320 of 36910