Date   

locked Re: Error message

Laurie, VK3AMA
 

On 18/04/2021 9:33 am, zl3trr@gmail.com wrote:

Ive just installed new version of jtalert on new windows 10 computer. I had jtdx running and then installed and the icon is on task manager at bottom of screen . When i hold mouse on blue icon , i can see jtalert 2.50.0 and my call sign but no actual pgm on screen  ?

when i click on blue icon it minimizes jtdx

Help please ?
Google "how to recover off-screen widow"

de Laurie VK3AMA


locked Re: Error message

Dwaine Pipe
 

Hi John

 

According to Dr Google :

You can do this by pressing Alt+Tab until that window is active or clicking the associated taskbar button. After you've got the window active, Shift+right-click the taskbar button (because just right-clicking will open the app's jumplist instead) and choose the “Move” command from the context menu.

 

Cheers

David

VK7YUM

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of zl3trr@...
Sent: Sunday, 18 April 2021 9:33 AM
To: Support@HamApps.groups.io
Subject: [HamApps] Error message

 

Ive just installed new version of jtalert on new windows 10 computer. I had jtdx running and then installed and the icon is on task manager at bottom of screen . When i hold mouse on blue icon , i can see jtalert 2.50.0 and my call sign but no actual pgm on screen  ? 

when i click on blue icon it minimizes jtdx 

Help please ? 

 

_


locked Error message

zl3trr@...
 

Ive just installed new version of jtalert on new windows 10 computer. I had jtdx running and then installed and the icon is on task manager at bottom of screen . When i hold mouse on blue icon , i can see jtalert 2.50.0 and my call sign but no actual pgm on screen  ? 

when i click on blue icon it minimizes jtdx 

Help please ? 

 


locked Re: LOTW Last Processed

Joe Subich, W4TV
 

Can you set it for 180 days?
One year is the current minimum (Settings -> Manage Settings -> Alerts
-> LotW/eQSL(AG) Flags). I agree - that setting should be "Months"
instead of years. Six (or even three) months is an appropriate minimum
these days.

73,

... Joe, W4TV


On 2021-04-17 6:00 PM, Steve Roth - AD4K wrote:
I, like others, have problems with those who have signed up with LOTW but
don't update their contacts. You have the time set for when their last
contact was for one year. Can you set it for 180 days? If they have
abandoned LOTW and have not updated for 180 days, I suspect they will never
update it.
LOTW makes proving the QSO contact a lot easier.
Great software, thanks SOOO much for your patience with the latest update.
Steve - AD4K


locked Re: JT Alert 2.50.0 update and now nothing works on JT Alert app

Laurie, VK3AMA
 

On 18/04/2021 3:31 am, Ed K0iL wrote:
I do not see the manager
That's the problem. Without the Manager running, nothing will work. It is critical to JTAlert operation.

de Laurie VK3AMA


locked Re: HamSpots #HamSpots

HamApps Support (VK3AMA)
 

On 18/04/2021 7:01 am, Russ - KA1ERL wrote:

Sorry about that.  Must have happened when I was testing out the new version of JTAlert and WSJT-X.

73

Russ (KA1ERL)


That's OK. I have on occasion had to go and block myself (so my bad spots are hidden) when I have inadvertently spotted the wrong band during testing.

de Laurie VK3AMA



locked Re: JT Alert 2.50.0 update and now nothing works on JT Alert app

HamApps Support (VK3AMA)
 

On 18/04/2021 8:30 am, Ed K0iL wrote:

I use both, but probably Edge on this one looking at history.  Yes, "Keep" was checked in each case.  I was testing if there was any Norton problem in the download so disabled Norton did another download.  That appeared with Norton Disabled, but downloaded file was identical to the first one.  Installed it with Norton Disabled.  Still didn't work.  So no Norton impact.  

Gave up on 2.50.0 and reinstalled last June's 2.16.7 with Norton restarted and changed back the WSJT-X settings.  It works again!  Made some contacts; it logged them automatically.  Everything works again on the older version.  I noticed I still have some Windows 10 virus and security stuff running.  But got burned out on trying to make this work on 2.50.0 at this point.  Whatever the problem is, might be time to look at GridTracker again.  For now, the old one works fine.  

Thanks to Laurie and yourself for responses and ideas.  


Are you certain you have the .NET 5 Desktop Runtime installed?
What does entering "dotnet" and "dotnet --info" produce when you type them into a Command Prompt window?
JTAlert 2.50.0 doesn't need to be installed to run those commands.
You should get something similar to this...
   


FYI, Disabling Norton, doesn't disable it completely. Norton has a long history of this behavior. One of the many reasons why many IT departments in the Corporate world long-ago abandoned Norton for PC Protection, myself included.

de Laurie VK3AMA


locked Re: JT Alert 2.50.0 update and now nothing works on JT Alert app

Ed K0iL
 

Jim, 

I use both, but probably Edge on this one looking at history.  Yes, "Keep" was checked in each case.  I was testing if there was any Norton problem in the download so disabled Norton did another download.  That appeared with Norton Disabled, but downloaded file was identical to the first one.  Installed it with Norton Disabled.  Still didn't work.  So no Norton impact.  

Gave up on 2.50.0 and reinstalled last June's 2.16.7 with Norton restarted and changed back the WSJT-X settings.  It works again!  Made some contacts; it logged them automatically.  Everything works again on the older version.  I noticed I still have some Windows 10 virus and security stuff running.  But got burned out on trying to make this work on 2.50.0 at this point.  Whatever the problem is, might be time to look at GridTracker again.  For now, the old one works fine.  

Thanks to Laurie and yourself for responses and ideas.  


locked Re: Loosing focus in the message window

Richard E. Ravich
 

Laurie,

Worked like a charm -- thanks for the help and everything you do for Ham Radio

73

WD6FIE - Richard

On 4/16/21 1:58 PM, HamApps Support (VK3AMA) wrote:
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


locked LOTW Last Processed

Steve Roth - AD4K
 

I, like others, have problems with those who have signed up with LOTW but don't update their contacts.  You have the time set for when their last contact was for one year.  Can you set it for 180 days?  If they have abandoned LOTW and have not updated for 180 days, I suspect they will never update it.

LOTW makes proving the QSO contact a lot easier.

Great software, thanks SOOO much for your patience with the latest update.

Steve - AD4K


locked Re: Do Callsign Alerts work with /MM callsigns?

HamApps Support (VK3AMA)
 

On 16/04/2021 1:21 am, Jim Reisert AD1C wrote:
Dave, I don't believe that grid squares factor into the Callsign Alert decision.  It should be an all-or-nothing decision based solely on the callsign.


If you have the B4 Alert set to consider Grids, than the /MM station CQing from a different from the previously logged Grid will be considered new (not a B4). That will cause the Wanted Callsign alert to be triggered. If a Callsign is detected as a B4 (based on the Mode, Band, Grid) setting for the B4 checks than ALL Alert types will not be triggered unless the B4 override for the individual Alerts is enabled.

In summary, if your B4 checks consider Grids as part of the alerting checks, a previously worked Wanted Callsign operating from a different grid will trigger the Wanted Callsign Alert.

de Laurie VK3AMA


locked Re: HamSpots #HamSpots

Russ - KA1ERL
 

Sorry about that.  Must have happened when I was testing out the new version of JTAlert and WSJT-X.

73

Russ (KA1ERL)

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, April 17, 2021 16:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] HamSpots #HamSpots

 

On 18/04/2021 2:45 am, Russ - KA1ERL wrote:

I am using wsjt-s v2.3.1 and JTAlert 2.50.0.
I am not seeing any of my spots or spots for me on HamSports.
Any idea what I am doing wrong?
Thank you for all you do for all the hams.
73
Russ (KA1ERL)


Simple, your callsign got blocked by one of the moderators for wrong band spotting. I note that the block has since been cleared and can see your outgoing spots, no incoming so you're likely no TX at this time.

de Laurie VK3AMA


locked Re: extra characters in my gridsquare

HamApps Support (VK3AMA)
 

On 18/04/2021 6:22 am, Dan Stoe via groups.io wrote:
I am getting two extra characters in my own gridsquare in QRZ log when I use JTAlert (v2.50 or 2.16.17) to copy my QSO data from WSJT-X (v2.3.1 0e7224) to QRZ.  My location is CN84jf.  This comes out as CN84JF50 when JSAlert updates my QRZ logfile.  When I just import WSJT-X ADIF from QRZ, all is well.

I've gone through all my settings multiple times but danged if I can figure out what I have misconfigured.  Help would be appreciated.

Dan Stoe
WB7NAM

Dan,

Something is not right, at most only the first 6 characters of a long grid will be logged. I will need to examine your JTAlert session files. Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: 2.5.0 Sounds "late"

Joe Subich, W4TV
 

I haven't seen any other reports of this. Well into the new period
delays should not be happening, there is nothing about the code that
should produce multi-second delays, at most a few ms.
I noted a sound alert at 13/15 in the *next* period again this
afternoon.

What sort of delays do you get when you use the "Test Sound Output"
menu?
In the first of four tests the sound was delayed 3 seconds. The other
three tests (immediately following) had no delay.

73,

... Joe, W4TV


On 2021-04-17 4:23 PM, HamApps Support (VK3AMA) wrote:
On 17/04/2021 10:57 pm, Joe Subich, W4TV wrote:
With 2.5.0 I find the alert sounds are often "late"... well into the
middle of the next transmit period.  If I'm not looking at the monitor
(and that's the whole reason for the sounds!), I've completely missed
the opportunity to call on that cycle.

Anything to speed up the sound or is that part of the old code that
hasn't been moved?

73,

  ... Joe, W4TV
That is not normal. Sound play is all within the .NET realm. It has been for many versions, prior to 2.50.0. The only change with 2.50.0 was the underlying .NET framework used.
I haven't seen any other reports of this. Well into the new period delays should not be happening, there is nothing about the code that should produce multi-second delays, at most a few ms.
What sort of delays do you get when you use the "Test Sound Output" menu? it behaves exactly like the queuing of sounds for triggered alerts, it is just the sound file specified that changes. Do you get delays with the test?
de Laurie VK3AMA


locked Re: dB Bug (JTAlert 2.5.0) ...

Joe Subich, W4TV
 

The dB checkbox is meant to be disabled if the Country checkbox is unchecked. A left-over from the code testing. Its corrected for the
next release.
OK, figured something like that was the case but when dB did not
display when selected, I decided to report it.

While the Lotw flag is obscured by the Badge when the Country line is
not shown, it is only partial, the flag can still be seen.
I increase the LotW flag size to see it. The overlap makes it much less
visible. Fortunately, I prefer to have the country and dB visible so
rarely use the "single line" layout.

Which flag is more important for you, Lotw or Eqsl?
I care not a whit about eQSL and had it turned off in previous versions.

73,

... Joe, W4TV


On 2021-04-17 4:16 PM, HamApps Support (VK3AMA) wrote:
On 17/04/2021 12:13 pm, Joe Subich, W4TV wrote:
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
The dB checkbox is meant to be disabled if the Country checkbox is unchecked. A left-over from the code testing. Its corrected for the next release.
While the Lotw flag is obscured by the Badge when the Country line is not shown, it is only partial, the flag can still be seen. This is a compromise I went with for the current release. Which flag is more important for you, Lotw or Eqsl? If it is LoTW, switch the display position of the badge to the right so it partially covers the Eqsl flag and not the Lotw flag.
In the early days of the new code, I had the Lotw and Eqsl flags shown as a single, dual pointed flag, with the point, left or right signifying the membership type. When dual pointed it indicated both memberships. The consensus of the Test Team was that is was too difficult to distinguish, I agreed with the assessment, so chose to go back to individual flags.
I have some thoughts on how better to display the QSL status, especially for "no Country display" users. but it is unlikely to be in the next release.
de Laurie VK3AMA


locked extra characters in my gridsquare

Dan Stoe
 

I am getting two extra characters in my own gridsquare in QRZ log when I use JTAlert (v2.50 or 2.16.17) to copy my QSO data from WSJT-X (v2.3.1 0e7224) to QRZ.  My location is CN84jf.  This comes out as CN84JF50 when JSAlert updates my QRZ logfile.  When I just import WSJT-X ADIF from QRZ, all is well.

I've gone through all my settings multiple times but danged if I can figure out what I have misconfigured.  Help would be appreciated.

Dan Stoe
WB7NAM


locked Re: DX Badge has odd letters

HamApps Support (VK3AMA)
 

On 18/04/2021 6:16 am, WarrenG KC0GU wrote:
The DX Badge show PHZR instead of DX.

Warren
KC0GU
_._,_._,

That's correct behavior.
2.50.0 doesn't restrict the "DX" badge to just "DX", it displays the actual direction word (1 to 4 alpha characters) of a directed CQ decode.

N4SO would have been sending "CQ PHZR N4SO grid"

Also I note the clipping of the flags in your image due to size. This has already been corrected for the next build, it was part of the code changes that allow for the online star to have its own size setting.

de Laurie VK3AMA




locked Re: 2.5.0 Sounds "late"

HamApps Support (VK3AMA)
 

On 17/04/2021 10:57 pm, Joe Subich, W4TV wrote:
With 2.5.0 I find the alert sounds are often "late"... well into the
middle of the next transmit period.  If I'm not looking at the monitor
(and that's the whole reason for the sounds!), I've completely missed
the opportunity to call on that cycle.

Anything to speed up the sound or is that part of the old code that
hasn't been moved?

73,

  ... Joe, W4TV

That is not normal. Sound play is all within the .NET realm. It has been for many versions, prior to 2.50.0. The only change with 2.50.0 was the underlying .NET framework used.

I haven't seen any other reports of this. Well into the new period delays should not be happening, there is nothing about the code that should produce multi-second delays, at most a few ms.

What sort of delays do you get when you use the "Test Sound Output" menu? it behaves exactly like the queuing of sounds for triggered alerts, it is just the sound file specified that changes. Do you get delays with the test?

de Laurie VK3AMA


locked Feature request

Fred Roberts
 

First.....love the new 2.50.0....it is great! I just have one suggestion due to older, not so good eyes....when a signal report is reported that has a leading zero, with the current display with the / through the zero, it is easily confused with an 8. Same with + or - 10 and 20. Can we have a zero without the / for signal reports?
Thanks for a great program, even if you can't get "regular" zeroes in the signal report field.
Fred
WB4QOC



Sent from my phone.....Fred


On Sat, Apr 17, 2021, 3:55 PM Laurie, VK3AMA <hamapps.support@...> wrote:


On 17/04/2021 2:16 am, Robert, SP8SN wrote:
> Tnx Laurie, I will send it soon.
>
> --
> Robert, SP8SN

Robert, files received. Thanks.

Check you email, I have sent a new build to try.
Let me know if it corrects the Callsigns window closing and opening.

de Laurie VK3AMA








locked Re: dB Bug (JTAlert 2.5.0) ...

HamApps Support (VK3AMA)
 

On 17/04/2021 12:13 pm, Joe Subich, W4TV wrote:
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

The dB checkbox is meant to be disabled if the Country checkbox is unchecked. A left-over from the code testing. Its corrected for the next release.

While the Lotw flag is obscured by the Badge when the Country line is not shown, it is only partial, the flag can still be seen. This is a compromise I went with for the current release. Which flag is more important for you, Lotw or Eqsl? If it is LoTW, switch the display position of the badge to the right so it partially covers the Eqsl flag and not the Lotw flag.

In the early days of the new code, I had the Lotw and Eqsl flags shown as a single, dual pointed flag, with the point, left or right signifying the membership type. When dual pointed it indicated both memberships. The consensus of the Test Team was that is was too difficult to distinguish, I agreed with the assessment, so chose to go back to individual flags.

I have some thoughts on how better to display the QSL status, especially for "no Country display" users. but it is unlikely to be in the next release.

de Laurie VK3AMA

2941 - 2960 of 37152