Another from my wish list: An option to allow splitting DX vs domestic call signs into separate partitions within the call sign window. Allow the user to turn the option on or off as they wish. What d

#FT8

Hello Laurie Some further info here. The County Hunting game is a bit divided at present. We have the CQ Magazine sponsored WACA which has been around for donkeys years but frankly has fallen into a b

#FT8

This thread is discussing Counties, the cublog lookup is for Countries <- note the "r". A subtle difference in spelling, but a significant difference in the lookup type. de Laurie VK3AMA

#FT8

Hello Laurie Gridtracker has alerts for counties and it works very well. I know they are the competition but as both JTAlert and Gridtracker are free, maybe they would be happy to divulge how they do

#FT8

Clublog has a very reliable and fast Callsign->DXCC conversion. See https://clublog.freshdesk.com/support/solutions/articles/167890-batch-lookups-of-dxccs. It has a bulk mode which will do the transla

#FT8

Just a thought...but what if each JTAlert user uploaded the QRZ data to hamspots.net and you could build your own database? Date tag the uploads...provide the database back to JTAlert users who could

#FT8

JTAlert does save any County data returned from an XML lookup when a QSO is logged. What is doesn't do is query the xml service for every decode received. Querying QRZ for the data of say 60 decodes r

#FT8

Incorrect. The progress-bar is an indicator of how many times they called. See the 2.50.0 features help file, Callsigns window topic for an explanation. de Laurie VK3AMA

#FT8

Rather than telling you what it is, I will tell you how to find out. Have a look in the 2.50.0 features help file under the "Callsigns window" topic. de Laurie VK3AMA

#FT8

If you are referring to the green thermometer, I think that shows how long they have been parked there with respect to how long before they are removed from the list. Dave, N2DPF

#FT8

Since the new update, I have seen where someone calling me shows up on the bottom. I like that part but I can’t find anything about the little bar under their call sign box. Can anyone tell me what th

#FT8

I have this on my todo list already. It will require reworking of the Callsigns window, replacing the existing divider between the main display and the Callers display with a user-dragable splitter al

#FT8

What I would like to see is a section similar to the "callers" display for specified alerts - New Grid, New DXCC and New CQ Zone (in my case). The alert would remain visible/active until worked, clear

#FT8

One up vote from me...I've had this problem too.... Thanks Laurie...things are really improving on all fronts.... Mike W9MDB

#FT8

I like the idea. With the old JTAlert Callsigns display, something like this would be a "definite no". With the flexibility the new UI creation code provides, it is a "qualified yes". I'll add it to t

#FT8

Here's one from my wish list. When monitoring the call sign window while working one station you might see another station you want to try when you're done with the first station but by the time you'r

#FT8

It simply takes too long to query QRZ for every US station in a decode period, evaluate that against a list of valid counties, and make a decision all in the 2-3 seconds between RX and TX periods. Tha

#FT8

I found it easier to use an external log that jtalert sends to and let it figure on county awards.

#FT8

I was under the impression JT Alert can query QRZ.com for other information and pull it into a log. QRZ has county information for most US hams. Why would this not be possible? 73 Bob Ko6Lu

#FT8

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 remo

#HamSpots #FT8 #JTDX