Date   

locked Re: Dark Mode

KB9HGI <kb9hgi@...>
 

Thanks Laurie for the update sounds cool!

 

Steve KB9HGI

 

Sent from Mail for Windows

 

From: HamApps Support (VK3AMA)
Sent: Thursday, October 28, 2021 9:42 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Dark Mode

 

On 29/10/2021 3:17 am, KB9HGI wrote:

Any plans for Dark mode on JT Alert? I run dark mode on wsjt-x  and everything else and JT-alert looks strange. Dark mode easier on the eyes to me


Yes there are plans.

Currently, color theming is in transition as I move the old code-base over to the new NET 5 code base.
The old code, the main JTAlert window will not change as eventually it will be gone completely. The new 2.50.x introduced windows already support custom coloring. There is no "Dark Mode" but you can adjust the colors of the different elements of a window to produce a dark effect.

The user-defined coloring as it currently exists, defined on a per-window basis, will be getting changed to a centralized theme coloring operation in the future when the remaining old JTAlert code is migrated. That theme/coloring will support saving & restoring custom user coloring along with predefined light & dark themes. That however is still some time away.

de Laurie VK3AMA

 


locked Re: Dark Mode

HamApps Support (VK3AMA)
 

On 29/10/2021 3:17 am, KB9HGI wrote:
Any plans for Dark mode on JT Alert? I run dark mode on wsjt-x  and everything else and JT-alert looks strange. Dark mode easier on the eyes to me

Yes there are plans.

Currently, color theming is in transition as I move the old code-base over to the new NET 5 code base.
The old code, the main JTAlert window will not change as eventually it will be gone completely. The new 2.50.x introduced windows already support custom coloring. There is no "Dark Mode" but you can adjust the colors of the different elements of a window to produce a dark effect.

The user-defined coloring as it currently exists, defined on a per-window basis, will be getting changed to a centralized theme coloring operation in the future when the remaining old JTAlert code is migrated. That theme/coloring will support saving & restoring custom user coloring along with predefined light & dark themes. That however is still some time away.

de Laurie VK3AMA


locked Re: Can not click on the call sign.

W8BBX John
 

Mike and Joe,

No I had not checked Settings/WSJT-X UDP Multicast on Loopback .
But I did. and now the operating state shows


UDP MCast on LB is now True, it was not before, but JTAlert was working before I did this.

Then I went to the WSJT Settings |Reporting and changed the server to 224.0.0.1.  That did not work, no CQ's showing on the Callsigns screen.
Then I went to the WSJT Settings |Reporting and changed the server back to 127.0.0.1.  That did  work, CQ's are showing on the Callsigns screen.

I left the checked, the Settings/WSJT-X UDP Multicast on Loopback .

And it still works.

Thank you
, folks.

W8BBX   John


locked Dark Mode

KB9HGI <kb9hgi@...>
 

Any plans for Dark mode on JT Alert? I run dark mode on wsjt-x  and everything else and JT-alert looks strange. Dark mode easier on the eyes to me


locked Re: Can not click on the call sign.

Joe Subich, W4TV
 

JTAlert Main Window Settings Menu ... top item. Check it.

See item 4 in Help -> WSJT-X UDP Setup

73,

... Joe, W4TV

On 2021-10-28 8:34 AM, John via groups.io wrote:
Still does not work.
I set the Wsjtx reply to Single click, it was set on Double click.
Photo WSJT-X Reporting.
.
Photo showing current screen on 224.0.0.1
File is from  About JTAlert  224.
How do I change the  JTAlert "Multicast on loopback"?
73  W8BBX


locked Re: Can not click on the call sign.

Michael Black
 


On the multicast setup did you check Settings/WSJT-X UDP Multicast on Loopback ?


Mike W9MDB


locked Re: Can not click on the call sign.

W8BBX John
 

IT Works.

I changed WSJT reporting to 127 AND checked the boxes.





File is from About  had to end JTAlert, then restart before it showed changes to WSJT-X reporting ( I think).


THANK YOU

W8BBX   John


locked Re: Can not click on the call sign.

W8BBX John
 

Still does not work.
I set the Wsjtx reply to Single click, it was set on Double click.
Photo WSJT-X Reporting. 
.

 Photo showing current screen on 224.0.0.1


File is from  About JTAlert  224.

How do I change the  JTAlert "Multicast on loopback"?

73  W8BBX


locked Re: New Release

Ken Bills
 

Thank for the update and great product.

73
Ken-W9KB


locked Re: New Release

HamApps Support (VK3AMA)
 

On 28/10/2021 4:29 am, Ken Bills via groups.io wrote:
Senior moment? I thought I read a post this past week about an upcoming new release with extensive changes. I can not seem to find the post. User files written to different directories etc.

73
Ken-W9KB

There have been no announcements of any upcoming release. I do make comment in some messages about fixes and changes that will be part of the next release, but there is never a date published ahead of time.

The HamApps.com website is the official source of JTAlert release downloads. The latest is 2.50.7

The only discussion about files in different directories was a brief comment by me in the Beta Group. I don't believe you're a member of that restricted group so if that was the source of your information it must have been passed on by one of the group members. Discussions in that group can often be wide-ranging about possible future functionality changes/enhancements/additions and don't necessarily reflect imminent changes.

Custom file-storage locations is on my todo-list, but not imminent, and definitely not for the next public release.

de Laurie VK3AMA
 


locked Re: Can not click on the call sign.

HamApps Support (VK3AMA)
 

On 28/10/2021 11:40 am, John via groups.io wrote:
I am new to JTAlert, but it works fine, except I can not click on the call sign and get WSJT_X to transmit the call sign.  I have to go to the WSJT screen and click on the call.
Did  |Help |UDP Setup, but I get nothing on the call screen, after the first one.
First time I tried the setup, click on the CQ on the Callsign and WSJT transmitted.

A photo of no call signs, WSJT_X revisions, JTAlert About.
 There is no WSJT-X UDP ID.


The attachment comes from  JTAlert About.
I changed back to 127.0.0.1, took out the checkmarks, and it works, except I still have to click on WSJT-X
Can anyone help.

John W8BBX

The About window not showing a UDP ID in the "Current Operating State" section indicates that JTAlert has never received a UDP message from WSJT-X. Unfortunately your image doesn't show all the status, so I am guessing that the "WSJT-X UDP MCast on LB" was showing false. While your WSJT-X UDP settings look fine, it is likely not having the JTAlert "Multicast on loopback" setting enabled is the cause of no UDP comms from WSJTX.

As for WSJTX not going into TX when a callsign is clicked or double-clicked (depending on how JTAlert is set) in JTAlert, that is controlled by WSJTX. JTAlert cannot direct WSJTX to go into transmit. If the DXCall is getting populated in WSJTX after a click event in JTAlert than JTAlert is behaving correctly in sending the appropriate instruction to WSJTX.

How do you have the JTAlert Callsigns window "Wsjtx reply" option set? Is it set to single or double click and is that how you're interacting with the callsigns? Perhaps you have it set to "Disabled"



de Laurie VK3AMA



locked Re: Can not click on the call sign.

Dave Garber
 

it looks like there may be some callsigns below the middle bar

Dave Garber
VE3WEJ / VE3IE


On Wed, Oct 27, 2021 at 8:57 PM John via groups.io <john.addis=yahoo.com@groups.io> wrote:
I am new to JTAlert, but it works fine, except I can not click on the call sign and get WSJT_X to transmit the call sign.  I have to go to the WSJT screen and click on the call.
Did  |Help |UDP Setup, but I get nothing on the call screen, after the first one.
First time I tried the setup, click on the CQ on the Callsign and WSJT transmitted.

A photo of no call signs, WSJT_X revisions, JTAlert About.
 There is no WSJT-X UDP ID.


The attachment comes from  JTAlert About.
I changed back to 127.0.0.1, took out the checkmarks, and it works, except I still have to click on WSJT-X
Can anyone help.

John W8BBX


locked Can not click on the call sign.

W8BBX John
 

I am new to JTAlert, but it works fine, except I can not click on the call sign and get WSJT_X to transmit the call sign.  I have to go to the WSJT screen and click on the call.
Did  |Help |UDP Setup, but I get nothing on the call screen, after the first one.
First time I tried the setup, click on the CQ on the Callsign and WSJT transmitted.

A photo of no call signs, WSJT_X revisions, JTAlert About.
 There is no WSJT-X UDP ID.


The attachment comes from  JTAlert About.
I changed back to 127.0.0.1, took out the checkmarks, and it works, except I still have to click on WSJT-X
Can anyone help.

John W8BBX


locked Re: Audio Alerts not playing

Jim Cary
 

Problem solved.  Somehow I had accidentally selected "out of shack" which kills the announcements.

73,

Jim


locked New Release

Ken Bills
 

Senior moment? I thought I read a post this past week about an upcoming new release with extensive changes. I can not seem to find the post. User files written to different directories etc.

73
Ken-W9KB


locked Re: Audio Alerts not playing

Jim Cary
 

Hi Michael,

Yes on both accounts!


locked Re: Audio Alerts not playing

Michael Black
 

I assume "Test Sound Output" works and you don't have sounds turned OFF?

Inline image





On Wednesday, October 27, 2021, 10:32:30 AM CDT, Jim Cary <jimlcary@...> wrote:


I just installed a second sound card to receive audio alerts and the card is functioning fine.  But the audio alerts are not being generated.  For example, if I have Needed States Alert set, the visual alert is generated, but not the audio alert.  If I pulse the "test" button on the setup page, I get the audio alert fine, so I know the audio side is working ok.  Attached are the settings for needed States Alerts.  What am I doing wrong?

Jim 
W2SM
JimLCary@...


locked Audio Alerts not playing

Jim Cary
 

I just installed a second sound card to receive audio alerts and the card is functioning fine.  But the audio alerts are not being generated.  For example, if I have Needed States Alert set, the visual alert is generated, but not the audio alert.  If I pulse the "test" button on the setup page, I get the audio alert fine, so I know the audio side is working ok.  Attached are the settings for needed States Alerts.  What am I doing wrong?

Jim 
W2SM
JimLCary@...


locked Re: JTAlert setup problem

HamApps Support (VK3AMA)
 

On 26/10/2021 2:18 am, jerry andersson wrote:
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

What does the non-working PC report in the JTAlert "Help -> About" menu window? Open the About window then copy the "Current Operating State" section of the window and past it into your reply. You can quickly copy to the clipboard by using the icon top-right of that section of the About window.



Also check that you have WSJTX and JTAlert UDP comms setup correctly. Open the help file via the "Help -> WSJT-X UDP Setup" menu and check that you have set both correctly.

de Laurie VK3AMA


locked Re: Flex Two slice WSJT-X Setup

HamApps Support (VK3AMA)
 

On 26/10/2021 8:34 am, Ken Bills via groups.io wrote:
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

Ken, Thanks for the update.

Unfortunately, you need to jump through these type of hoops and expense because of how N1MM has been coded. It doesn't support multicast UDP. Multicast UDP when enabled allows for multiple applications to work with WSJTX concurrently without interference to other participating applications. The N1MM developer has chosen deliberately not to implement multicast UDP (his words not mine), so without your sort of workaround N1MM will block any other application trying to work with WSJTX.

FWIW, implementing multicast UDP is a trivial task, taken a handful of code lines, easily supported in the language N1MM is coded. Why the N1MM developer is refusing to implement this user-friendly change is unknown.

de Laurie VK3AMA

1121 - 1140 of 38435