|
|
Post by K7GQ on Apr 2, 2022 17:04:47 GMT
Setting Notifications to "highlight worked ones" results in every call being flagged as previously worked. Since this doesn't appear to be an issue with other users, I'm wondering if this is a result of my ADI file having exceeding 15K records, possibly exceeding the internal table size. If this is indeed the case, what is the ADI file limit?
Thanks
|
|
|
|
Post by Arvo ES1JA on Apr 2, 2022 18:00:23 GMT
What is in Your opinion "worked one", for JTDX is "worked one" this callsign which is not matched to any configured New. Nothing to do with log file size.
|
|
|
|
Post by K7GQ on Apr 2, 2022 20:53:53 GMT
I assume that JTDX, like WSJT, considers a "worked one" when that call is found in the ADIF.
|
|
|
|
Post by Arvo ES1JA on Apr 3, 2022 6:31:53 GMT
You assume not correctly, JTDX is completely different in this area. You should in Settings/Notificatios enable Highligthing New calls and also per band and per mode to get result You wanted.
|
|
|
|
Post by Fred k1io on Jun 21, 2022 4:21:27 GMT
This is a problem. For a while I wouldn't use JTDX because it showed everyone as "B4". "Worked one" is not really what green means; it means CQ/73 not in an earlier activated category, which could include new calls. I turned on "new call" and only then were the residual green ones really new ones. Better labeling would really make a difference. And a rescan button (like WSJT-X has) wouldn't hurt either. As it stands it confuses new users who take it literally.
|
|
|
|
Post by Arvo ES1JA on Jun 21, 2022 5:40:04 GMT
Once again. All qso info is taken from wsjtx_log.adi file. B4 is determined by qso NOT falls into any determined New notification. Showing B4 with own background is possible but not reccommended, for this other attributes are better. With full color background are displayed only CQ and 73 like messages (If selected) because then user can quick select new correspondent who is “free”. JTDX-s autoselect should do it faster. In JTDX is essential to set New notifications correctly first, would say that having New calls per band and per mode set is essential for most users.
If this principle is not for You then forget using JTDX.
|
|
|
|
Post by Fred k1io on Jun 21, 2022 18:06:01 GMT
My point is not that the behavior of JTDX is wrong, but that it is labeled incorrectly so that it appears to be wrong. JTDX is a derivative of WSJT-X and its user interface has some good improvements (mainly the bigger receive window due to much better use of space). But the green last entry is not "B4" but as you said "not in any (other) determined notification", which means it can be new or old. There is a corresponding function in WSJT-X and when you use a similar label, position, and color, people expect similar behavior. Change the label and it's correct -- the behavior is not bad, just confusing if you have not turned on the right set of other colors.
|
|
|
|
Post by g4xcq on Feb 8, 2023 17:12:59 GMT
Hello everyone. Nice to be accepted onto the forum.
First of all I am no computer expert (too old)!
With the help of my local ARC I was successful in installing JTDX on my old (Windows 8) computer and it seemed to work fine.
I upgraded my PC to a Windows 11 machine, downloaded a fresh copy of JTDX which uploaded successfully. However it would not transmit my signal on my full power setting (20 W).
I obtained a further copy of JTDX from a fellow member of my local ARC loaded it into my PC and it works perfectly, (even better than my first installation).
However the strike through function for previous contacts seemed to start again from a new beginning as if I had not made any contacts with any received signals at all?
I am using the same ADIF logfile as before which shows my contacts from day one but my "new" JTDX version does not recognise any contacts from my old setup. Is this normal or is there a way of telling my new version to read all of my stored log?
Sorry this is longwinded and not technical but can my new version be commanded to read all of my existing log?
|
|
|
|
Post by Fred k1io on Feb 11, 2023 16:38:43 GMT
Make sure you have a "full" wsjt_log.adi file in the JTDX directory. If the reinstall put in a new one, find the old one. It may also take a little while for a new installation to make use of the file -- I did have a problem once when nothing was shown as worked_b4 until it ran for a while, though now it is fine.
Since I also have WSJT-X installed (who doesn't?), and I want the same file to work for both, I set up a Hard Link in one directory to the file in the other. So I have one file literally in both directories. Microsoft doesn't talk about that feature much, which is better known on Unix, but it works.
|
|
