Date   

locked Re: Callsign window has some problems

Laurie, VK3AMA
 

On 17/04/2021 4:08 am, Joe Subich, W4TV wrote:

Well, you can always disable the callers list all together since the
callers are duplicated in the main display.  Click on the gear icon
or press F2, then select Callers and choose "Disabled" in the "Display
Position" box.

With your single line, you might also be able to choose Left or Right
and divide the long single line.

I use a tall and narrow Callsigns window since it fits my display real
estate better than a horizontal display so I have room to allow one
short line of "callers" at the bottom of the display.

73,

  ... Joe, W4TV
You beat me to my response, which essentially says the same, but not as clear in the detail.

de Laurie VK3AMA


locked Re: Callsign window has some problems

Laurie, VK3AMA
 



On 17/04/2021 1:59 am, WB5JJJ - George wrote:
Thanks for you suggestion Joe.  But I desire to use a minimalist single line display for this as with earlier versions.  I'll live with the pop UNDER for lower priority items to keep it to one line.  Don't need a 2nd line that will be mostly empty space occupying real estate.  Besides the calling me calls are duplicated in both lines anyway just wasting space.  

JTA filters all the chaff from the wheat for me, leaving just new LoTW callers and wanted DXCC, New Prefix and a couple other alert items.  A quick glance tells me all I really need to know in the moment, while WSJTx BA shows me the rest, if I'm interested.  
--
73's
George - WB5JJJ

If you want single line only, which will automatically show a vertical scroll bar when the number of callsigns exceeds the space available, you need to have the Callers display position set to either "Right" or "Left", NOT "Top" or "Bottom".

If you're not interested in seeing the Callers in a separate view of the Callsigns window (where they persists and don't clear at the end of a period) then set the Callers display position to "Disabled"

   

de Laurie VK3AMA
 


locked Re: JTAlert 2.50.0

Michael Black
 

What version of WSJTX or JTDX are you using?

Mike W9MDB




On Friday, April 16, 2021, 01:02:40 PM CDT, Angus G0UGO <angus.g0ugo@...> wrote:


That’s exactly what’s happening with me

 

Angus G0UGO

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Walter Reinert
Sent: 16 April 2021 16:15
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.50.0

 

When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: Callsign window has some problems

Joe Subich, W4TV
 

Well, you can always disable the callers list all together since the
callers are duplicated in the main display. Click on the gear icon
or press F2, then select Callers and choose "Disabled" in the "Display
Position" box.

With your single line, you might also be able to choose Left or Right
and divide the long single line.

I use a tall and narrow Callsigns window since it fits my display real
estate better than a horizontal display so I have room to allow one
short line of "callers" at the bottom of the display.

73,

... Joe, W4TV

On 2021-04-16 11:59 AM, WB5JJJ - George wrote:
Thanks for you suggestion Joe.  But I desire to use a minimalist single line display for this as with earlier versions.  I'll live with the pop UNDER for lower priority items to keep it to one line.  Don't need a 2nd line that will be mostly empty space occupying real estate.  Besides the calling me calls are duplicated in both lines anyway just wasting space.
JTA filters all the chaff from the wheat for me, leaving just new LoTW callers and wanted DXCC, New Prefix and a couple other alert items.  A quick glance tells me all I really need to know in the moment, while WSJTx BA shows me the rest, if I'm interested.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: JTAlert 2.50.0

Angus G0UGO <angus.g0ugo@...>
 

That’s exactly what’s happening with me

 

Angus G0UGO

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Walter Reinert
Sent: 16 April 2021 16:15
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.50.0

 

When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: JTAlert 2.50.0

Steve H.
 

I got the same issue. It happens when a variable is used but not declared first . 


On Fri, Apr 16, 2021, 11:15 Walter Reinert <nj8g@...> wrote:
When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G

Attachments:


locked Re: JTAlert - 73 Badge

Jim Cooper
 

On 16 Apr 2021 at 12:19, Craig wrote:

Do have a question - when the 73
decode badge window appears, was it
intended that double-clicking would
not enable TX? Do not see the
option on this.
my experience is that clicking on a call
showing the 73 badge SETS UP the
messages for that call in WSJT-X, but
does not enable the Enable Tx (which seems
reasonable, as the operator should decide
when to start calling a 'tail ender' call --
if you don't have the Tx freq locked, you
would start calling on top of the ending
part of the current QSO).

When you click on a call with the CQ badge,
it does enable Enable Tx because it's known
that you want to start calling right away.


locked Re: Issues after moving to a new Win10 PC

Phil Cooper
 

Hi Joe,

 

Thanks for that, but I am not a member of that group, so am unable to post there.

 

Perhaps Bill G4WJS is monitoring this, and can advise?

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Joe Subich, W4TV" <lists@...>
Sent: Friday, 16 April, 2021 15:52
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Issues after moving to a new Win10 PC


On 2021-04-16 10:34 AM, Phil Cooper via groups.io wrote:

> When I start WSJTx, I'm told there is an issue with rig control, and
> that I need to have HamLib installed.

Hamlib is a library that is installed as part of WSJTX. See the WSJTX
group <main@WSJTX.groups.io> for assistance with that program.

73,

... Joe, W4TV


On 2021-04-16 10:34 AM, Phil Cooper via groups.io wrote:
>
> Hi all,
>
> I've just set up a new Win10 Pro 64bit PC in the shack, and I am having issues with WSJTx.
>
> When I start WSJTx, I'm told there is an issue with rig control, and that I need to have HamLib installed.
> Well, I have downloaded that, but it fails to install on Win10, so now I am stuck...
>
> Any pointers to getting this all working please?
>
> 73 de Phil GU0SUP
>







locked JTAlert - 73 Badge

Craig
 

GM.  First, Congratulations on 2.5  Great implementation.  Do have a question - when the 73 decode badge window appears, was it intended that double-clicking would not enable TX?   Do not see the option on this.  Thanks again.


locked Re: Callsigns window disappears and reappears after a while

Robert, SP8SN
 

On Thu, Apr 15, 2021 at 12:30 PM, HamApps Support (VK3AMA) wrote:
I have installed the new version 2.50. Everything works OK but there is a problem with the "callsigns" window. It displays the decoded characters and disappears after a few dozen seconds, reappears by itself after a few seconds. I have two programs running for two transcivers. It is the same in both. What's the problem
Tnx Laurie, I will send it soon.
 
--
Robert, SP8SN


locked Re: Callsign window has some problems

WB5JJJ - George
 

Thanks for you suggestion Joe.  But I desire to use a minimalist single line display for this as with earlier versions.  I'll live with the pop UNDER for lower priority items to keep it to one line.  Don't need a 2nd line that will be mostly empty space occupying real estate.  Besides the calling me calls are duplicated in both lines anyway just wasting space.  

JTA filters all the chaff from the wheat for me, leaving just new LoTW callers and wanted DXCC, New Prefix and a couple other alert items.  A quick glance tells me all I really need to know in the moment, while WSJTx BA shows me the rest, if I'm interested.  
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked JTAlert 2.50.0

Walter Reinert
 

When operating JTAlert 2.50.0 it will decode, but after a minute or two I get this attached message and the Main JTAlert window closed
Attached System info

Me
--
Walt NJ8G


locked Re: Issues after moving to a new Win10 PC

Joe Subich, W4TV
 

On 2021-04-16 10:34 AM, Phil Cooper via groups.io wrote:

When I start WSJTx, I'm told there is an issue with rig control, and that I need to have HamLib installed.
Hamlib is a library that is installed as part of WSJTX. See the WSJTX
group <main@WSJTX.groups.io> for assistance with that program.

73,

... Joe, W4TV


On 2021-04-16 10:34 AM, Phil Cooper via groups.io wrote:
Hi all,
I've just set up a new Win10 Pro 64bit PC in the shack, and I am having issues with WSJTx.
When I start WSJTx, I'm told there is an issue with rig control, and that I need to have HamLib installed.
Well, I have downloaded that, but it fails to install on Win10, so now I am stuck...
Any pointers to getting this all working please?
73 de Phil GU0SUP


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

Ed K0iL
 

Looked at File Insight; 

Startup Item = No  (cannot change this)

User Trusted was Don't Trust.  (I changed this to Trust Checked) 

Developers = Not Available (this may be a problem in trust since it is so brand new time wise) 

Few Users = Fewer than 100 users

73, de ed -K0iL


locked Re: Callsign window has some problems

Joe Subich, W4TV
 

Increase the *HEIGHT* of your callsigns display to display a
second row.

Notice in Screen 1, 3 and 4 there is a gray line at the *TOP*
of the callsigns display. In Screen 2 that line is at the
*BOTTOM* of the callsigns display.

That gray line separates the "calling me" section of the window
and the "alerts" section. You need at least two rows in the
callsigns window otherwise the "calling me" section will overlay
the "alerts" (general callsigns) area.

73,

... Joe, W4TV

On 2021-04-16 10:19 AM, WB5JJJ - George wrote:
Caught it happening.
Screen 1 is the calling me on top of 2 announced wanted prefix callsigns.
Screen 2 is after I clicked the "x" and it shows what was hidden.
Screen 3 same as 1 with different stations.
Screen 4 same as 2 with different stations.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Issues after moving to a new Win10 PC

Phil Cooper
 

Hi all,

 

I've just set up a new Win10 Pro 64bit PC in the shack, and I am having issues with WSJTx.

 

When I start WSJTx, I'm told there is an issue with rig control, and that I need to have HamLib installed.

Well, I have downloaded that, but it fails to install on Win10, so now I am stuck...

 

Any pointers to getting this all working please?

 

73 de Phil GU0SUP


locked Another Callsign Window Issue

Tom Job
 

Good morning, all...

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


locked Re: Callsign window has some problems

WB5JJJ - George
 

Caught it happening.  

Screen 1 is the calling me on top of 2 announced wanted prefix callsigns.
Screen 2 is after I clicked the "x" and it shows what was hidden.
Screen 3 same as 1 with different stations.
Screen 4 same as 2 with different stations.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: Callsign window has some problems

WB5JJJ - George
 

The 1,2,3 are positions from the left side of the Callsign Window.  

I sent you a support request so you will have my settings and such to check.  

--
73's
George - WB5JJJ
Hamshack Holine #4969


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

Ed K0iL
 

Laurie, 
I just checked and I did load the 32 bit because it's (x86) which is was my other ham apps are installed at.  

So why isn't the JTAlertV2.Manager Application running as installed?  Hmmm.

73, de ed -K0iL

4321 - 4340 of 38444