Date   

locked Re: api-ms-win-crt-runtime-l1-1-0.dll missing ->> try reinstalling the program to fix

HamApps Support (VK3AMA)
 

On 14/04/2021 11:15 am, Jim wrote:

[Edited Message Follows]

after installing JTAlert 2.50.0 on my windows 7 computer I get this message.  What did I do incorrectly and how do I fix it?
This is a new installation of JTAlert of course and the new .net seems to work or at least I didnt get any errors from it.
Yes I know reinstall it, but I have done that multiple times and it didnt install the file needed.  What do I do now?

Jim K3ybn
Per the subject line, this is a very common problem with Windows. A quick Google search results in hundreds of thousands hits. You appear to be missing the Microsoft Visual C++ 2015 Redistributable. Either it has been removed from your PC or its installation is faulty.

JTAlert doesn't have any C++ code so doesn't need this, but the .NET runtime installer likely does, but that is only a guess. Many applications need this, so it is worthwhile getting your system updated into a good state.

de Laurie VK3AMA


locked View Dec odes window gone

John Holmes W9ILY
 

With the new version, the "View Decodes" window is no longer there. I have found this window very useful so when I receive an alert of a wanted call, state, etc. and I'm not looking at the current decodes window I can scroll back to see what was decoded and where. The callsign causing the alert is colored differently so it's easy to find. Laurie, can this be restored?
John W9ILY


locked Re: 2.5.0 -- AutoIt Error

David - AK2L
 

> I suggest you make sure your HRD version is the latest
It is the latest

> and if the problem persists, contact HRD support
I'll solve the real problem (I hope) by installing Maria DB and then I can use JTAlert's features again.


locked Re: Transmit frequency

HamApps Support (VK3AMA)
 

On 14/04/2021 9:37 pm, Ernie Barnhart wrote:

I thought in earlier versions when ctrl-clicking a callsign in JTAlert that  it passed that key combination on to WSJT-X that changed the transmit frequency to the receive frequency. The new version only appears to be passing the click key (not ctrl combination) to WSJT-X.

Thank you again for all you do. 

de Ernie N8DVE

Ernie,

My error, you're correct about the ctrl-click. I never use it so had forgotten about it.

I just did a quick visual scan of the new code, I never implemented the keyboard modifier test for the callsign click event in this new release. I should have it fixed for the next release.

Sorry about that.

de Laurie VK3AMA


locked Re: Large folder!

HamApps Support (VK3AMA)
 

On 14/04/2021 11:17 pm, Bill - AA4M wrote:
I just discovered that this folder:

C:\Users\mrbil\AppData\Local\HamApps\AA4M\config\JTAlertX

Contains 110MB of files dating from today all the way back to 08/22/21.  Is there any reason I can't delete all this as part of my periodic housekeeping?

73, Bill  AA4M

Bill,

Those old files should be getting removed automatically and only the last 7 days of backups should be retained.

What version of JTAlert are you running?

You can safely delete the files containing a date & time in their filename. BUT do not delete config.sqlite, that is your live settings file.

de Laurie VK3AMA


locked Re: Restoring the summary line in the new Call Signs Window

HamApps Support (VK3AMA)
 

On 15/04/2021 1:15 am, Jim - N4ST wrote:

Select the window and press F2 to bring up the options for that window.


Correct. This works for all the windows, F2 is the standard across all the windows (current and future) for opening the Options/Settings .

de Laurie VK3AMA


locked Re: activity window

HamApps Support (VK3AMA)
 

On 15/04/2021 2:28 am, f8nhf wrote:
I can't find the activity window 
even with the help I can't find it 
in the setup JTAlert section <windows/Activity is activated

thank you for your help

73 Denis F8NHF

"View -> Activity window" menu of the main JTAlert window. Or press F11 when the main JTAlert window is active (has focus).

de Laurie VK3AMA


locked Re: CQ Marathon Alert in v2.5.0 - Defect confirmed

HamApps Support (VK3AMA)
 

On 15/04/2021 2:40 am, W6XK wrote:
I frequently hover the cursor over a call sign to quickly obtain basic info about the received station, including the type of alert (if any) generated for that station.  This is helpful when more than one alert is generated for a specific station, because only the highest priority alert is color-coded.  In the former version, one or more alerts were listed in the pop-up window under the list of station info.  In v2.5.0, a needed alert is now text-highlighted, rather than listed below the station info.  How can I get a CQ Marathon alert to be shown in the pop-up window in the latest version?

Vy 73, Chet W6XK

Chet,

Tnx for the report. I can confirm this is a defect.

The Callsign tooltip does have Marathon alerted entries, but they do not display if there is no Marathon triggered status set in the data feed from the old JTAlert (where all the alerting logic still resides) and the new Callsigns window. The Marathon triggered data is not being received because it is not being sent, this is the defect. I am investigating. I should have it fixed for the next release.

de Laurie VK3AMA
 


locked Re: icon messaging #FT8

HamApps Support (VK3AMA)
 

On 14/04/2021 4:45 pm, f8nhf wrote:
you are right, for the message alert to be visible I have to increase the size of the flag to 10 at this size the window is not fluid anymore 
your idea to add a control if it is feasible or put a badge instead
 greetings

73 Denis F8NHF

FYI, the next JTAlert has a dedicated size selector for the Online (Star) icon. The size of the icon no longer uses the QSL flag size. This has already been coded and tested.

de Laurie VK3AMA


locked Re: 2.50.0 not logging propagation data

HamApps Support (VK3AMA)
 

On 14/04/2021 9:21 pm, Ron W3RJW via groups.io wrote:
2.50.0 not logging propagation data ... Item is ticked in "Logging" options.  Has been working in previous versions.

TNX
--
73
Ron, W3RJW

This is a defect. See my response at https://hamapps.groups.io/g/Support/message/34175

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

HamApps Support (VK3AMA)
 

On 15/04/2021 1:45 am, David - AK2L wrote:
Follow up to #34151
Here is an example of logging two calls with myself:

The first and third entries are from JTAlert.  The second and fourth are from WSJT-X.
The date, grid and submode are all missing.

That looks like a previously reported HRD Logbook bug.

HRD in their infinite wisdom chose to implement an ADIF parser that requires the fields in a QSO record to be in a specific order and it breaks when it receives the ADIF data from JTAlert. The ADIF files, per the official ADIF specs, do not need the data to be in a specific order, it is not a CSV file where order is mandatory. HRD eventually acknowledged this defect rather than continually blaming JTAlert, and promised a fix. Either the fix has not been forthcoming or your running an old HRD version.

I tried matching the adif field order of the WSJT-X adif data, to work around this bug, but that failed because JTAlert includes additional data, like name, QTH, Solar data, State, Zones, etc that WSJT-X does not provide, and I was flying blind not knowing what the expected order was, it is not documented.

I suggest you make sure your HRD version is the latest and if the problem persists, contact HRD support end inquire about when the adif field order defect will be corrected.

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

Bob Frostholm
 

Whoops... I apologize,,,,sorry to waste your time.

73

Bob

Ko6Lu
On 4/14/2021 11:18 AM, Laurie, VK3AMA via groups.io wrote:



On 15/04/2021 4:07 am, Bob Frostholm wrote:
Why does my Logging Options page look different than yours?

Do you really want an answer?

The difference is that my screen-capture shows the checkbox display scrolled down to reveal the settings that were not in view. Note my image had a red rectangle around the scrollbar and part of my message read "(you will need to scroll the window down to find the setting)".

de Laurie VK3AMA


--
Bob
KO6LU


locked Re: Call Sign Display Grid Disappeared

Thomas Webb
 

Problem solved!!!   In the 'View' menu, I clicked 'Call Sign Window' and it came back.

Tom, WA9AFM


locked Re: Callsign window

Paul Nicholson
 

I upgraded JTAlert yesterday, and found that double-clicking on callsigns in the Callsign window and Decodes window does not flow back to WSJT-X (v2.3.1) on my Win10 computer, which has all the current patches and has been rebooted.  Is this what you're seeing?
To test this, I just downgraded to JTAlert 2.16.17 and saw the same thing. I wonder if this isn't caused by a Windows update.
In both cases, WSJT-X seems to work as expected and JTAlert windows are populating properly but I'm unable to cause action in WSJT-X from mouse clicks in JTAlert.


locked Re: Solar Data Not Logged? - Defect Confirmed.

HamApps Support (VK3AMA)
 

On 15/04/2021 1:15 am, Jim - N4ST wrote:

Ver 2.50.0 does not seem to be logging solar data to HRD Logbook.

And I do have the box checked to do so in the JTAlert Settings.

 

Also, in the options for the Activity Window, the “Solar in the Title Bar” check box works just the opposite of what is implied.

A clear box posts the data, a checked box removes the data.

 

_________

73,

Jim – N4ST


Jim,

Tnx for the report. This is a defect.

It has been corrected for the next release.

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

Laurie, VK3AMA
 



On 15/04/2021 4:07 am, Bob Frostholm wrote:
Why does my Logging Options page look different than yours?

Do you really want an answer?

The difference is that my screen-capture shows the checkbox display scrolled down to reveal the settings that were not in view. Note my image had a red rectangle around the scrollbar and part of my message read "(you will need to scroll the window down to find the setting)".

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

Bob Frostholm
 

Laurie

Why does my Logging Options page look different than yours?

73

Bob

Ko6Lu
On 4/13/2021 4:45 PM, HamApps Support (VK3AMA) via groups.io wrote:

On 14/04/2021 6:51 am, David - AK2L wrote:
Note: I did try to have JTAlert send (UDP) the QSO to HRD, but HRD was not picking up the submode from a MFSK/FT4 QSO whereas it picked it up from WSJT-X just fine.

Likely you haven't set the "Log FT4 as ADIF 3.1.0 ..." setting under the Logging Options (you will need to scroll the window down to find the setting).



de Laurie VK3AMA


--
Bob
KO6LU


locked Call Sign Display Grid Disappeared

Thomas Webb
 

While experimenting with some of the settings in 2.5, I unclicked 'On Top' for the Call Sign Display Grid thinking this would get rid of the tool bar display.  However, the Call Sign Display Grid is gone and I can't find how to get it back.

Tom, WA9AFM


locked Re: Can't find call sign window

Brad@...
 

Well I thought I’d give you an update. When I went to delete the “callsign” file there was nothing there, I discovered that if I changed the “main” monitor though it suddenly appeared, so I’m not sure why but seems to be working.


locked CQ Marathon Alert in v2.5.0

W6XK
 

I frequently hover the cursor over a call sign to quickly obtain basic info about the received station, including the type of alert (if any) generated for that station.  This is helpful when more than one alert is generated for a specific station, because only the highest priority alert is color-coded.  In the former version, one or more alerts were listed in the pop-up window under the list of station info.  In v2.5.0, a needed alert is now text-highlighted, rather than listed below the station info.  How can I get a CQ Marathon alert to be shown in the pop-up window in the latest version?

Vy 73, Chet W6XK

4581 - 4600 of 38533