Date   

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


locked Loosing focus in the message window

Richard E. Ravich
 

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


locked Re: Callsign window has some problems

Laurie, VK3AMA
 

On 17/04/2021 5:35 am, WB5JJJ - George wrote:
A great space saver would be to eliminate the duplicated callers in the 2nd area would make it even better.
In addition to my last message, the duplication of the Caller callsigns, one in the main view, and one in the Callers view, is similar to how WSJT-X displays decodes. A Calling station will show under both the "Band Activity" left list and the "Rx Frequency" right list with the decode in the left list typically scrolling out of view in a few seconds while remaining much longer in the less populated right list. JTAlert behaves similarly in the persistence of the Callsigns.

The choice to not see the Callers in a separate view is in your hands, just disable the view. JTAlert offers a lot of user-choice.

de Laurie VK3AMA


locked Re: Callsign window has some problems

Laurie, VK3AMA
 

On 17/04/2021 5:35 am, WB5JJJ - George wrote:
A great space saver would be to eliminate the duplicated callers in the 2nd area would make it even better.
The Callers area, by design, only contains stations calling you, it does not auto-clear like the main view at the end of a period. It allows you to see past Callers that you have not worked. Its a convenience feature for those users who tend to generate small pile-ups.

If you don't want the convenience of seeing past callers, how often they called, and when they last called, when they may no longer be visible in the main display, simple, disable the Callers display.

de Laurie VK3AMA


locked Re: Callsign window has some problems

Joe Subich, W4TV
 

On 2021-04-16 3:35 PM, WB5JJJ - George wrote:

A great space saver would be to eliminate the duplicated callers in the 2nd area would make it even better.
Easy enough to eliminate (or disable) - from my prior response:

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.
73,

... Joe, W4TV


On 2021-04-16 3:35 PM, WB5JJJ - George wrote:
That works very well. I was just was not totally clear as to what the options did.
A great space saver would be to eliminate the duplicated callers in the 2nd area would make it even better.
Again a great program and love the new layout.
--
73's
George - WB5JJJ
Hamshack Holine #4969


locked Re: "Callers" Display v2.50.0

HamApps Support (VK3AMA)
 

On 17/04/2021 5:42 am, HamApps Support (VK3AMA) via groups.io wrote:
It will be an easy fix, taking a lot less time than producing this message, hi.

I'll send you a new build to test, likely in a couple of hours.

Ron,

I spoke too soon. It wont be an easy fix, I now realize why I went with that design of the Callers view scrolling horizontally when it is at the Top of the Bottom of the main display. Its complicated.

Needless to say, there wont be a fix in the short term.

I have some thoughts on how to resolve, but it will take some time (hours or days depending on my work-load).

Sorry for prematurely getting your hopes up.

de Laurie VK3AMA
 


locked Re: "Callers" Display v2.50.0

HamApps Support (VK3AMA)
 

On 17/04/2021 4:38 am, Ron W3RJW via groups.io wrote:
In order to save screen space my "Callsigns" decoded window is arranged to be 2 columns wide, with rows from top to the bottom of the screen.  The "callers" display is a neat feature, but when you select the display position to be "bottom" (for instance) I only see at most two of the callers.  If there are more then two (often), they propagate off Callsigns display to the right.  I guess I expected that they would fill up from the bottom. two columns wide or whatever the width of the window was set to.

I don't know if that's possible or even practicable.

Thanks for some great new features.

--
73
Ron, W3RJW

Ron,

I can confirm the behavior.
I wont classify as a defect, just an inappropriate design choice on my part. This is one of the problems when testing with dummy data and not getting on-air for live testing, but that's what the Test Team is for ;).

When the Callers view is set to Bottom or Top of the main view, to accommodate overflow the Callsigns are scrolled horizontally, not vertically like the main view. This should have been set to vertical scrolling.

It will be an easy fix, taking a lot less time than producing this message, hi.

I'll send you a new build to test, likely in a couple of hours.

de Laurie VK3AMA


locked Re: Callsign window has some problems

WB5JJJ - George
 

That works very well. I was just was not totally clear as to what the options did.  

A great space saver would be to eliminate the duplicated callers in the 2nd area would make it even better.  

Again a great program and love the new layout.  

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


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

HamApps Support (VK3AMA)
 

On 16/04/2021 11:27 pm, Ed K0iL wrote:
So why isn't the JTAlertV2.Manager Application running as installed?  Hmmm.

The Manger is installed, it is your Norton protection software that is interfering with its execution.

See https://hamapps.groups.io/g/Support/message/34373

de Laurie VK3AMA


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

HamApps Support (VK3AMA)
 

On 16/04/2021 11:25 pm, Ed K0iL wrote:
JTAlertV2.Manager Application is installed in the pluginsX folder, but it is not running per Task Manager.

If it is not running that is the problem.

JTAlert automatically tries to restart the program if it is found not running. If you're not seeing the Manager process being started and stopped approx every 2 seconds, that indicates that something is clamping down very hard on it getting executed.

You mention Norton in one of your other message. That will be the problem. Depending on Norton settings, low-use
(based on Norton users-base counts) files, which Ham based applications are, suffer from lack of reputation and Norton is notorious for this time of reputation application blocking. You will need to set Norton to consider JTAlert safe, and likely remove any blocks it has already put in place.

Sorry, I can't offer any informed advice on how to setup Norton to stop its inappropriate blocking, you're best to engage with Norton support direct.

de Laurie VK3AMA


locked Re: JTAlert 2.50.0

HamApps Support (VK3AMA)
 

On 17/04/2021 1:15 am, Walter Reinert 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

Walt,

Another user had a similar issue, different line number. It was ultimately resolved by deleting the JTAlert config file. I suspect some setting within the file is the root cause, unfortunately neither my self or the Test Team have encountered the error.

Try temporarily renaming the JTAlert config file so that when JTAlert starts it creates a new file. Does the error occur after doing that?

The JTAlert help file (NOT the 2.50.0 features help file),  "Troubleshooting -> Setting Changes Not Remembered" section discusses where the config file is located and also how to roll-back to an earlier version of the config if needed. The help file can be access via the "HamApps JTAlert" Windows start-menu group if you're unable to from within JTAlert.

If JTAlert still throws the error despite being started without a config file, my suggestion at this time is to rollback to JTAlert 2.16.17

If JTAlert stops throwing the error after renaming the config.sqlite file, please zip it up and send to me direct (not via this group) so I can try and reproduce the problem.

Let me know your results.

de Laurie VK3AMA


locked Re: JTAlert - 73 Badge

HamApps Support (VK3AMA)
 

On 17/04/2021 4:38 am, Craig wrote:
Thanks Jim for your note / comments. Yes, sure seems reasonable to me that clicking on a 73 Badge would enable TX... that is the intent of showing the 73 badge - but as far as I can tell it doesn't work, and it is not obvious (as yet) that there is an option to make it work.  Should operate as CQ Badge does...

Maybe Laurie can add some perspective on this...

73, Craig

I already answered here https://hamapps.groups.io/g/Support/message/34362

I cant make JTAlert perform a WSJT-X function that WSJT-X itself does not support. I'm good, but not that good ;-)

de Laurie VK3AMA

3001 - 3020 of 37153