Date   

locked Re: "db" font small

HamApps Support (VK3AMA)
 

On 26/10/2021 11:41 pm, Ron W3RJW via groups.io wrote:
Laurie, This is a very small knit pick:  The font size of the "db" report is much smaller then the rest of the text in the 'Callsigns' decode display.
Does not seem to follow other text changes.



--
73
Ron, W3RJW

Ron,

The reduced size of the db report compared to the Country name on the same line of the display was a deliberate design decision. My thinking at the time was to have any data prefixing the Country name to be of a different size so there was a visual separation of the two values. The plan was to offer alternate data items to be displayed in the db position. That never happened and with a db report not likely to be confused as part of the Country name there is really no need to have the reduced size. I have made the font size change for the next release, it is now equal to the Country name font size.

de Laurie VK3AMA


locked Re: "db" font small

Joe Subich, W4TV
 

Laurie,

Noticed the same thing here ... only it seems to be related to
the presence of Badges/Flags. When, particularly, both a badge
and a flag are present, the second line is rendered in a much
smaller type face than when the badges and flags are not. It
seems the presence of a badge *or* a flag reduces the size of
the second line by one step and the presence of *both* reduces
the second line by two steps.

In my opinion, the second line should take precedence over the
badges/flags. There will only be one badge at a time so it
does not need to extend below the first line and I am just
fine with the second line covering the eQSL and Online flags
(I don't show them anyway).

73,

... Joe, W4TV

On 2021-10-26 8:41 AM, Ron W3RJW via groups.io wrote:
Laurie, This is a very small knit pick:  The font size of the "db" report is much smaller then the rest of the text in the 'Callsigns' decode display.
Does not seem to follow other text changes.
--
73
Ron, W3RJW


locked "db" font small

Ron W3RJW
 

Laurie, This is a very small knit pick:  The font size of the "db" report is much smaller then the rest of the text in the 'Callsigns' decode display.
Does not seem to follow other text changes.



--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x Improved Widescreen 2.5.1, JTAlert 2.50.7, HRD Deluxe v6.7.0.391
FTdx-3000, SignaLink USB


locked Re: logging problem

Ed Ireland
 

Thanks Laurie.  You led me to the problem.  When I upgraded WSJT-X to v2.5.1 (at the same time I upgraded WSJT-X to v2.5.1), the “Logging” option “Prompt me to log QSO” became unchecked.  Sorry for blaming it on JTAlert!

 

Thanks for your great App!

 

Ed K5YZW

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) via groups.io <vk3ama.ham.apps@...>
Date: Monday, October 25, 2021 at 6:17 PM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] logging problem

On 26/10/2021 1:55 am, Ed Ireland wrote:

I recently installed JTAlert 2.50.7 and it no longer logs to DXKeeper, a problem that I have not had through all the upgrades.  Under "Logging" and "DXLab DXKeeper, "Enable DXLab KXKeeper Logging" is checked.  What am I missing?  Should I revert back to version 2.50.6?

Thanks for your help.

Ed K5YZW


Downgrading JTAlert is not likely to help. The DXKeeper logging code is unchanged.

Are you hitting the "OK" button of the WSJTX "Log QSO" window, if not that would be the reason for non-logging. JTAlert will not receive a logged QSO event from WSJTX if you're not completing the logging action in WSJTX.
JTAlert TCP logging instructions to DXKeeper may be getting blocked by your firewall.
Check that the DXKeeper Network Service is not running, check the "Default" tab of DXKeeper Configuration window.
   
If DXKeeper is showing "See DXKeeper Errorlog.txt" in its title bar, check that as it may contain the reason for the non-logging.

de Laurie VK3AMA


locked Re: logging problem

HamApps Support (VK3AMA)
 

On 26/10/2021 1:55 am, Ed Ireland wrote:
I recently installed JTAlert 2.50.7 and it no longer logs to DXKeeper, a problem that I have not had through all the upgrades.  Under "Logging" and "DXLab DXKeeper, "Enable DXLab KXKeeper Logging" is checked.  What am I missing?  Should I revert back to version 2.50.6?

Thanks for your help.

Ed K5YZW

Downgrading JTAlert is not likely to help. The DXKeeper logging code is unchanged.

Are you hitting the "OK" button of the WSJTX "Log QSO" window, if not that would be the reason for non-logging. JTAlert will not receive a logged QSO event from WSJTX if you're not completing the logging action in WSJTX.
JTAlert TCP logging instructions to DXKeeper may be getting blocked by your firewall.
Check that the DXKeeper Network Service is not running, check the "Default" tab of DXKeeper Configuration window.
   
If DXKeeper is showing "See DXKeeper Errorlog.txt" in its title bar, check that as it may contain the reason for the non-logging.

de Laurie VK3AMA


locked Re: logging problem

Ed Ireland
 

Yes, I rebooted many times but no change.  Any other ideas?

 

Thanks,

 

Ed K5YZW

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of AB8WD-Willie via groups.io <AB8WD@...>
Date: Monday, October 25, 2021 at 10:28 AM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] logging problem

Did you try rebooting pc?


locked Re: Flex Two slice WSJT-X Setup

Ken Bills
 

Finally managed desired setup:

2 instances of JTAlert/WSJT-X and two active slices with Flex 6500 AND N1MM for dupe checking across different bands, callsign verification, etc. This required a third party TCP/UDP port splitter program. The secret (which took all day to discover) was splitting the secondary UDP server port and forwarding to N1MM. Splitting the main UDP port server interfered with JTAlert's operation (no alerts forwarded to WSJT). It's a less than elegant solution, but works for me.

The third party program was way too expensive, but I did manage to get  a 50% 'educational' discount.

https://www.aggsoft.com/tcp-splitter/

Thanks to Laurie VK3AMA for offering some help on how to open the second instance of JTAlert.

73
Ken-W9KB


locked JTAlert setup problem

jerry andersson
 

Hi 
I have two QTH's where I'm active 
 
"summerhouse" installed JT Alert 2-50.7- JTDX, on a win10pro - running FB.
 
Home QTH win7pro , 6GB,x64, net5.0 desktop
JT Alert working OK with JTDX, but can't get JT Alert to show anything in Callsign, QSO history, Macros...
 the Messaging window functions !
Tried to revert back to a version pre 2.50 where the macros window functioned - lost that communication too.
Evidently I have managed to do something that I shouldn't. Any suggestions are welcome
73 Jerry
SM7BZV / SM6BZV / SI6V
 


locked Re: logging problem

AB8WD-Willie
 

Did you try rebooting pc?


locked logging problem

Ed Ireland
 

I recently installed JTAlert 2.50.7 and it no longer logs to DXKeeper, a problem that I have not had through all the upgrades.  Under "Logging" and "DXLab DXKeeper, "Enable DXLab KXKeeper Logging" is checked.  What am I missing?  Should I revert back to version 2.50.6?

Thanks for your help.

Ed K5YZW


locked Re: Flex Two slice WSJT-X Setup

Ken Bills
 

Thanks... will give it a try.

73
Ken-W9KB


locked Re: Decodes windows - Always On Top

sq3rx
 

The latest one works correctly.
Thanks.


locked Re: Decodes windows - Always On Top

sq3rx
 

Hi Laurie,
Not sure did you receive my mail
Unfortunately version which you sent me, didnot work. I got window with information that JTAlertSettings.exe was missing


locked Re: JT Alert display #HamSpots

HamApps Support (VK3AMA)
 

On 25/10/2021 1:28 am, Rémy Wenger via groups.io wrote:
Same issue here, working on Windows 11

What issue? What are you not seeing?

If you're referring to the log fields area of the main JTAlert window is not being displayed, use the "View -> Show Log Fields" menu.

de Laurie VK3AMA


locked Re: Callers Panel

Lloyd - W1LBM
 

Laurie,

Thank you. That corrected my problem.  I know it must be something that I had not configured correctly.

73 Lloyd - W1BM


locked Re: Callers Panel

Onaka JA4JOE
 

You can send it by checking here.


locked Re: JT Alert display #HamSpots

Rémy Wenger
 

Same issue here, working on Windows 11


locked Re: Strange new Continet Alert

Stewart Wilkinson
 

Thanks.


locked Re: Callers Panel

Lloyd - W1LBM
 

Thank you for your quick reply.  As you suggested I reviewed the "Accept UDP", this was and always has been checked.  Below I'm including a partial screenshot from this morning of what I and seeing.  The Callsigns #1 panel is clickable but the Caller and possibly the Alerts Only panels are not clickable.

Lloyd - W1LBM

JTDX Settings 2.2.0-rc155


From JTAlert 2.50.7


locked Re: Strange new Continet Alert

Ron W3RJW
 
Edited

On Sun, Oct 24, 2021 at 05:18 AM, Stewart Wilkinson wrote:
Where do I find those settings ? - I am looking but I don't see them.
Set for each category:



Also you need to be connected to an enabled log.
 
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x Improved Widescreen 2.5.1, JTAlert 2.50.7, HRD Deluxe v6.7.0.391
FTdx-3000, SignaLink USB

1141 - 1160 of 38435