Date   

locked Re: Ver 2.50.0 issues

Bill Barrett
 

Hello Laurie-

  Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Yes, saw that, Very COOL!
Looking forward to additional enhancements, Elon Musk calls them Easter Eggs.

73;

Bill W2PKY

On Wed, Apr 14, 2021 at 7:53 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 15/04/2021 9:26 am, Bill Barrett wrote:
Or one window with multiple partitions? Okay, hope you get a laugh [or at least a giggle] out of this.

73. Bill W2PKY

Not as far-fetched as you think. Are you aware the Callsigns window already has an additional partition that display Stations calling you?

Rather than multiple partitions, perhaps one additional partition with the ability for the user to assign what sort of decodes appear there, say CQs or 73s or a specific Alert type (like Dxcc or State) with the ability for the Callsigns to persist for a period of time (ie they don't automatically get cleared at the end of a period like the main display partition).

The beauty with the new code and desktop UI creation tools is the flexibility it gives me in adding new functionality with minimal fuss, aka headaches. Not that this is an acknowledgement of what you propose will happen, but I am not apposed to the idea.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0 upgrade Callsign Window

OM Marlon, DW3CWM
 

 

Hi Laurie,

 

JTDX is set to auto log qso. If that may somehow affect this. JTalert is set to Auto Clear when JTDX decodes are cleared, in application. I find this setting as a ggod preparation for LOG4OM to log the QSO.

 

I tried to clear that option, it leaves the last qso in the callbox of LOG4OM, but clicking/double clicking the caller in the callsign window will not trigger JTDX to transmit. It is not a problem, the list in itself helps me manage a pile up of sorts.

 

Thanks 73 de DW3CWM, Marlon

 

Sent from Mail for Windows 10

 

From: HamApps Support (VK3AMA)
Sent: Saturday, 17 April 2021 2:41 am
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.50.0 upgrade Callsign Window

 

On 16/04/2021 8:24 pm, OM Marlon via groups.io wrote:

I can click / double click callsigns and jtdx would respond. 

 

I was referring to my station callers, they will now be listed, multiple if several others called too, below callsign list. After concluding qso with a callsign listed in callers, i was wondering if, by just clicking the other callers listed, i can trigger jtdx. That woul have been nice, but for now use it to remind me, the callsigns i have not concluded qso, the will all be listed in users. I hope I described the situation better hihi. Thanks

 

Marlon


I understand.

The callsigns in your Callers display behave the same as the callsigns in the main Callsigns display with respect to click/double-clink events. Both events use the exact same code internally.

Are you clearing decodes in JTDX regularly?

If a Callsign in JTAlert is clicked, WSJT-X and JTDX will not respond if the original decode for that Callsign is no longer available.

Are you clicking older callsigns that have had their original decode cleared in JTDX?

de Laurie VK3AMA

 


locked Re: JTAlert 2.50.0 not connecting to wsjt-x or JTDX but as connected to Log4om #JTDX

Dave Garber
 

I have mine working with wsjtx-Jtalert- and then to log4om2, also have in there a udp to gridtracker, and then on to n3fjp ( as my backup to the backups), on another computer.  I am not using multicast

Dave Garber
VE3WEJ / VE3IE


On Fri, Apr 16, 2021 at 10:30 PM Joe Subich, W4TV <lists@...> wrote:

For WSJTX to connect to *both* JTAlert and Log4OM you will need to
use a multicast UDP address in WSJTX.  See the "WSJTX UDP Setup"
topic in the JTAlert "Frequently Asked Questions" (HELP).

73,

    ... Joe, W4TV


On 2021-04-16 10:00 PM, Darin Snell via groups.io wrote:
> I have been using a  older version of JTAlert with no issue, but I have downloaded v. 2.50.0 and I'm getting this message. I'm not the most computer literate but the ports match and it is connected to Log4om. just having a issue connecting to WSJT-X or JTDX. I'm wondering if i should go multicast or not.
>
>







locked Re: JTAlert 2.50.0 not connecting to wsjt-x or JTDX but as connected to Log4om #JTDX

Joe Subich, W4TV
 

For WSJTX to connect to *both* JTAlert and Log4OM you will need to
use a multicast UDP address in WSJTX. See the "WSJTX UDP Setup"
topic in the JTAlert "Frequently Asked Questions" (HELP).

73,

... Joe, W4TV

On 2021-04-16 10:00 PM, Darin Snell via groups.io wrote:
I have been using a  older version of JTAlert with no issue, but I have downloaded v. 2.50.0 and I'm getting this message. I'm not the most computer literate but the ports match and it is connected to Log4om. just having a issue connecting to WSJT-X or JTDX. I'm wondering if i should go multicast or not.


locked dB Bug (JTAlert 2.5.0) ...

Joe Subich, W4TV
 

Laurie,

If one turns off the "Country" display in the Callsigns window,
the dB (signal report) is also eliminated even if it is selected.
Also, if "country" is not displayed, the "badge" obscures the
LotW or eQSL flag depending on which side the badge is set to
display.

73,

... Joe, W4TV


locked JTAlert 2.50.0 not connecting to wsjt-x or JTDX but as connected to Log4om #JTDX

Darin Snell
 

I have been using a  older version of JTAlert with no issue, but I have downloaded v. 2.50.0 and I'm getting this message. I'm not the most computer literate but the ports match and it is connected to Log4om. just having a issue connecting to WSJT-X or JTDX. I'm wondering if i should go multicast or not.


locked Re: V 2.50.x Observations

K0GU
 

Now we will see how well I really read the help file. Is there anyway to soften the background color of the call sign window(s). It used to be slightly greyed out. Maybe it still is and I can't tell. But I have 3x LARGE JTAlert windows running and that is a lot of bright. I turned the monitor brightness down a bit more than I would like for my bandscope.

Nag, nag, nag. Sorry :o)

--
73,  Jay  K0GU


locked Re: V 2.50.x Observations

K0GU
 
Edited

OK thanks guys and a thousand pardons. I finally read the "JTAlert 2.50 features" help file included with the new version and have adjusted a number of things. Not too tough if I was smart enough to RTFM first.

73,  Jay  K0GU


locked Re: JTAlert 2.50.0

Walter Reinert
 

Laurie

Followed you instruction, still received error except different line number attached, going back to 2.16.17


--
Walt NJ8G


locked Re: Access newest Help file prior to installation?

neil_zampella
 

Sorry ... I could have sworn I had two versions installed at one time.

 

My bad,

 

Neil, KN3ILZ


locked Re: JTAlert 2.50.0

Walter Reinert
 

Mike

Running:

WSJT-X v2.3.0 0c42df
HRD 6.7.0.323 Release 6.7.0.323
--
Walt NJ8G


locked Re: Another Callsign Window Issue

Tom Job
 

Hi Laurie…

 

Yes, something that didn’t occur to me was the CPU load.  I am using an old Acer Aspire E1-522, 6GB of RAM but only a 1.4GB CPU, dual core.  I watched the task manager for a while and the decode period is just about maxing the CPU!  So, it can’t keep-up on 20m, at least, with 40 or 50 decodes per cycle.

 

I have an Apple MacBook Pro (i7 CPU and 8GB RAM) that was given to me and it already has Parallels installed on it.  Parallels creates a VM on Apple so you can run Linux/Windows etc.…  It’s a lot newer that the Acer, more RAM and has a better CPU.  I’ll setup a VM and run Windows that way.   I know its sacrilege to run Windows on an Apple but I’m already going to hell, so why not?! J

 

73 Laurie and thanks….Tom VE3II 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (Vthe first 5 secondsK3AMA)
Sent: April 16, 2021 14:36
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Another Callsign Window Issue

 

On 17/04/2021 12:26 am, Tom Job wrote:

I have noticed that the callsign window does not always clear the old callsigns.  I have experienced the window populating 6 or 7 decode cycles before clearing. It's not a constant issue but rather an intermittent one. This is the first version of JTAlert that I have seen this.  Of course, I can clear it with the escape key but that shouldn't have to be done.  Could it be a Windows "thing"?  I am using Windows 8.1.

Has anyone else experienced this? 

Thanks....Tom VE3II


I have not seen any other reports of this behavior. It might be win8.1 related, but I am inclined to think a PC capability issue perhaps since you're running Win8.

What are your hardware specs, CPU core count, installed Ram?

What CPU usage numbers (percentage) are you getting at the end of a decode period when WSJT-X is at its busiest?

Is WSJT-X still displaying decodes from the previous period when the new period starts?

When this occurs, is it on very busy bands, like 20m & 40m where there are dozens of decodes per period?

de Laurie VK3AMA




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Thanks for JTAlert Improvements

Don AA5DE
 

Thanks for the many improvements in JTAlert. Especially the change of font which allows dim eyes to distinguish O and Q and other pairs.

--
AA5DE, Don
D. L. (Don) Eddy
[dleddy@aya.yale.edu]
Georgetown, Texas


--
Don Eddy AA5DE


locked JTAlert Test Team vacancies, I'm recruiting.

HamApps Support (VK3AMA)
 

I have some vacancies on the Test Team.

If you're computer literate, have been using JTAlert for a few years, and are prepared to participate in the Test Team discussions, and not just wanting to get early access to new releases, send me an email with some detail of you're Windows/JTAlert setup and experience.

Now that the new .NET based code has been publicly released I expect the momentum of new functionality and replacement of the old code-base to increase. More eyes & hands on the changes will help greatly.

My expectations are that Test Team members will use the new JTAlert builds in a live setting and provide feedback of what is not working or needs changes. Feature suggestions are also encouraged. I don't expect members to perform rigorous testing of all functionality of JTAlert every time there is a new build. I am reasonably comfortable with code changes that are made before I create a new build, but bugs creep in. Having more eyes and hands on the new product helps avoid those going public.

Salary for Team members is non-negotiable, everyone gets the same base amount, $0 ;-)

Send a direct email to vk3ama.ham.apps [at] gmail.com

I will likely not reply directly to most requests. If you receive a group join email, you made the cut.

de Laurie VK3AMA


locked Re: V 2.50.x Observations

HamApps Support (VK3AMA)
 

On 17/04/2021 7:13 am, K0GU wrote:
The Callsigns window like all the new 2.50.0 windows support zooming (text scaling), up to 200%.
  Is this in JTAlert or Windows?

  Can I get rid of the country name being displayed and taking up an extra line? 

  Sorry if these have been answered before. I have been accused of not being able to see the forest for the trees (American slang I guess). 

73,  Jay  K0GU

Text scaling is within the JTAlert realm. It is independent of any Windows system-wide scaling you have set.

The JTAlert 2.50.0 introduced windows can be scaled independently of other JTAlert windows. For example, I have the Band Heat set at 170% so I can see it from across the room, while the Callsigns window is at 110%.

Getting rid of the Country line is easy, uncheck the "Country" checkbox under the "Options" popup of the Callsigns window. You will see the effect of the change in real-time, like 99% of all the option/settings of the new 2.50.0 windows.
   

I strongly recommend going through the "JTAlert 2.50.0 features" help file, its not overly large and easy to navigate with lots of images. All of what you asked is covered in that file.

de Laurie VK3AMA




locked Re: V 2.50.x Observations

Joe Subich, W4TV
 

Can I get rid of the country name being displayed and taking up an extra line?
Yes, in the Callsigns window click the gear icon or strike F2. Select
Callsigns and *uncheck* "Country".

73,

... Joe, W4TV


On 2021-04-16 5:13 PM, K0GU wrote:
On Wed, Apr 14, 2021 at 01:25 PM, HamApps Support (VK3AMA) wrote:


The Callsigns window like all the new 2.50.0 windows support zooming (text
scaling), up to 200%.
Is this in JTAlert or Windows?
Can I get rid of the country name being displayed and taking up an extra line?
Sorry if these have been answered before. I have been accused of not being able to see the forest for the trees (American slang I guess).
73,  Jay  K0GU


locked Re: "Callers" Display v2.50.0

Ron W3RJW
 

Understand.  Thanks Laurie
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.0, HRD Deluxe v6.7.0.323
FTdx-3000, SignaLink USB


locked Re: V 2.50.x Observations

K0GU
 

On Wed, Apr 14, 2021 at 01:25 PM, HamApps Support (VK3AMA) wrote:
The Callsigns window like all the new 2.50.0 windows support zooming (text scaling), up to 200%.
  Is this in JTAlert or Windows?

  Can I get rid of the country name being displayed and taking up an extra line? 

  Sorry if these have been answered before. I have been accused of not being able to see the forest for the trees (American slang I guess). 

73,  Jay  K0GU


locked Re: .net.50 download

Jim Cary
 

Laurie,

When I tried today, everything worked fine.  Same download URL, etc.  Microsoft must have had a slight problem yesterday.

73,

Jim


locked Re: Loosing focus in the message window

HamApps Support (VK3AMA)
 

On 17/04/2021 6:25 am, Richard E. Ravich wrote:
I noticed that I loose focus in the message window when wsjtx decodes another time period.  Is there a way to keep the focus on the message window?
Upgrade to the latest version went perfectly -- thanks Laurie for all you do!
73's
WD6FIE - Richard

Turn off the WSJT-X "To Top" setting in the Settings window of the main JTAlert window. Under the "Applications -> WSJT-X / JTDX" section of the Setting. Either turn off or change it to only occur on certain Alerts triggering.

   

de Laurie VK3AMA

2821 - 2840 of 36984