Date   

locked Re: Callsigns window appeared too small to be usable and readjusted

HamApps Support (VK3AMA)
 

On 29/04/2021 12:17 am, Gary Yarbrough via groups.io wrote:
Okay it happened again this morning and I am attaching the two files.

73, Gary
KE5TD

Tnx Gary!

The files indicate that the small size of the window is due to incorrect values being recorded in the config file and then being applied when next starting. Specifically, the size recorded was ...
    "Width": 160.0,
    "Height": 28.0,

These values are very wrong. There is likely a defect somewhere in the code causing this, but what and where is the question.

Is there anything unusual in your shutting down of JTAlert? How do you perform the JTAlert shutdown or do you leave it running and discover the incorrect size when you return to your PC?

de Laurie VK3AMA




locked Re: Q65 decodes not showing

K0GU
 

I don't see any Q65 calls in the JTAlert window either. But I thought that wasn't enabled yet from an earlier announcement. So I haven't been trying. I just worked someone on Q65 and nada in the window.
--
73,  Jay  K0GU


locked Re: Callsigns window appeared too small to be usable and readjusted

Gary Yarbrough, KE5TD
 



On Monday, April 26, 2021, 02:58:37 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/04/2021 5:08 am, Gary Yarbrough via groups.io wrote:

I also had the same experience two days, but I used the F3 key to resize and it has not repeated.

Gary
KE5TD

Gary,

If this occurs again, if your able, I would appreciate getting a copy of the Callsigns window config files before you resize the window. I need to see what sizes are recorded in the files when this occurs.

The files are "Callsigns_1.config" and "Callsigns_1.config.json" and are located at %localappdata%\HamApps\JTAlert\
KE5TD\Config\

The files are small, ~3KB.

Thanks
de Laurie VK3AMA

Laurie,

Okay it happened again this morning and I am attaching the two files.

73, Gary
KE5TD


locked Re: unable to launch program

dpaschal@...
 

OM (name?, callsign?) - I am not certain what you mean here.  Callsign is WB4IHY

What version of Windows, 7.1, 8.1 or 10? 10 - latest update.
What bit type 32bit (x86) or 64bit (x64)? x64

Check TaskManager, is JTAlertV2,Manager.exe running?  None of these are running.  I rebooted too.


locked Re: unable to launch program

HamApps Support (VK3AMA)
 

On 28/04/2021 11:45 am, dpaschal@... wrote:
I have been using LOG4OM2 now and wanted to start using JTAlert after not using it for a month or so as I am trying to chase specific states and countries and like the functionality for that.  When I try to launch JTAlert, I get the following error every time:

OM (name?, callsign?)

What version of Windows, 7.1, 8.1 or 10?
What bit type 32bit (x86) or 64bit (x64)?

Check TaskManager, is JTAlertV2,Manager.exe running?

de Laurie VK3AMA


locked unable to launch program

dpaschal@...
 

I have been using LOG4OM2 now and wanted to start using JTAlert after not using it for a month or so as I am trying to chase specific states and countries and like the functionality for that.  When I try to launch JTAlert, I get the following error every time:
https://i.imgur.com/CRbsBMx.png


locked Re: Clear decodes window on startup?

Phil Cooper
 

Hi Laurie,

 

Ah, I saw that, but completely misinterpreted it!

I missed the Startup Options at the top. Booking a trip to the opticians now!

 

73 de Phil GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: 27 April 2021 17:55
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Clear decodes window on startup?

 

On 28/04/2021 2:07 am, Phil Cooper via groups.io wrote:

When I was running v2.16.17 on my old Win7 box, I am sure I had set the decodes window to "clear on startup", but I cannot seem to find that option in v2.50.0.
Was that just my imagination, or was it an option?

Am I missing something somewhere? I have looked in the decodes window "settings", and the settings in JTAlert, but I cannot find it anywhere.

I know I am getting old, but surely my memory isn't that bad?

73 de Phil GU0SUP


The 2.50.0 Decodes window is unchanged from earlier releases.
The Delete All setting is where it has always been, under the Decodes Settings window.

   

de Laurie VK3AMA


locked Re: Clear decodes window on startup?

HamApps Support (VK3AMA)
 

On 28/04/2021 2:07 am, Phil Cooper via groups.io wrote:

When I was running v2.16.17 on my old Win7 box, I am sure I had set the decodes window to "clear on startup", but I cannot seem to find that option in v2.50.0.
Was that just my imagination, or was it an option?

Am I missing something somewhere? I have looked in the decodes window "settings", and the settings in JTAlert, but I cannot find it anywhere.

I know I am getting old, but surely my memory isn't that bad?

73 de Phil GU0SUP


The 2.50.0 Decodes window is unchanged from earlier releases.
The Delete All setting is where it has always been, under the Decodes Settings window.

   

de Laurie VK3AMA


locked Clear decodes window on startup?

Phil Cooper
 

Laurie and the group,

When I was running v2.16.17 on my old Win7 box, I am sure I had set the decodes window to "clear on startup", but I cannot seem to find that option in v2.50.0.
Was that just my imagination, or was it an option?

Am I missing something somewhere? I have looked in the decodes window "settings", and the settings in JTAlert, but I cannot find it anywhere.

I know I am getting old, but surely my memory isn't that bad?

73 de Phil GU0SUP


locked Re: 2.5.00 Error in combination with HRDLog.net and HRDLog

Stefan Braun
 

Dave, why should HRD be wrong? It worked since years before JTAlert 2.5. And it works again when I downgrade. I work with JTAlert since I don´t know which version, Since more then 3 years i would say.
So it should have been a bug in JTAlert 2.5.0. Or if 2.5.0 is now ok then all other versions where wrong and due to my configuration it worked.

Nothing special configured in JTDX and also not in JTAlert. 


locked Re: Missing .dll file #FT8 #JTDX #TIP

Ron Schunk
 

Hi..glad to help with a what I can since I"ve gotten so much help off the forum(s)...
73's
Ron
WA8KQF

On Sun, Apr 25, 2021 at 2:22 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 26/04/2021 3:00 am, Ron Schunk wrote:
Been having problems getting JTAlert to work with JTDX....got that message about the missing .dll file api-ms-win-crt-runtime-l1-1-0.dll ....reloaded JTAlert after downloading and installing the C++ MS file and .NET 5.0 Runtime as suggested...still didn't work, so I went out and did a duckduckgo.com search and found a page that directed me to Microsoft for a download of Windows 8.1 KB2999226-x64 (using Windows 8.1 64 bit op sys)...installed that and rebooted and everything is working fine now...
Thanks for all the suggestions..
Ron
WA8KQF

Thanks for the tip.

de Laurie VK3AMA


locked Re: Callsigns window appeared too small to be usable and readjusted

Gary Yarbrough, KE5TD
 



On Monday, April 26, 2021, 02:58:37 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/04/2021 5:08 am, Gary Yarbrough via groups.io wrote:

I also had the same experience two days, but I used the F3 key to resize and it has not repeated.

Gary
KE5TD

Gary,

If this occurs again, if your able, I would appreciate getting a copy of the Callsigns window config files before you resize the window. I need to see what sizes are recorded in the files when this occurs.

The files are "Callsigns_1.config" and "Callsigns_1.config.json" and are located at %localappdata%\HamApps\JTAlert\
KE5TD\Config\

The files are small, ~3KB.

Thanks
de Laurie VK3AMA

RRR and I missed typed F2 key!

Gary
KE5TD


locked Re: Callsigns window appeared too small to be usable and readjusted

Steven Fook
 

On Mon, Apr 26, 2021 at 03:00 PM, HamApps Support (VK3AMA) wrote:
On 27/04/2021 12:56 am, Steven Fook via groups.io wrote:

I don't know if anybody experienced this or documented it, but when I opened JTAlert 2.50 this morning, the callsigns window appeared like this:




Previously it displayed nice and big in all its glory, and I did not touch any settings to modify anything in the program since I installed the update a while back.
Is there anyway to get to the properties other than the gear icon that now I cannot access?

Thanks!

Steven

Steven,

That is unexpected. I'm not sure how it came to that. There have not been any similar reports.

All the settings for the Callsigns window are held in a single config file. It includes the window size, position and zoom settings. Your image shows that the previous session position and zoom settings were restored correctly, but not the window size, indicating that the config file hadn't been removed or corrupted. I'll investigate and try to reproduce the effect.

As to unlocking the size without access to the gear icon, simple, click the Callsigns window to make it the active window then press the F2 key. That will open the Options popup and you will be able to unckeck the "Size locked" checkbox (under the "Window" section of the Options), you will then be able to drag the window borders to resize.

BTW, the F2 key is standard across all the JTAlert windows for opening their Options popup.

de Laurie VK3AMA

Laurie, that did the trick.  I was able to restore it to my previous size using F2.  I had the 'size locked' option checked, so naturally I was unable to simply resize the window using the resize cursor.

On Mon, Apr 26, 2021 at 02:49 PM, Joe Subich, W4TV wrote:
Is there anyway to get to the properties other than the gear icon
that now I cannot access?
Like any other Window ... grab the lower right corner with your mouse
and pull to the size you desire.
Unfortunately when the "Size locked" option is checked in the settings, you cannot resize it simply with the mouse.

73,
Steven K2EJ


locked Re: Callsigns window appeared too small to be usable and readjusted

HamApps Support (VK3AMA)
 

On 27/04/2021 5:08 am, Gary Yarbrough via groups.io wrote:

I also had the same experience two days, but I used the F3 key to resize and it has not repeated.

Gary
KE5TD

Gary,

If this occurs again, if your able, I would appreciate getting a copy of the Callsigns window config files before you resize the window. I need to see what sizes are recorded in the files when this occurs.

The files are "Callsigns_1.config" and "Callsigns_1.config.json" and are located at %localappdata%\HamApps\JTAlert\
KE5TD\Config\

The files are small, ~3KB.

Thanks
de Laurie VK3AMA


locked Re: Callsigns window appeared too small to be usable and readjusted

Gary Yarbrough, KE5TD
 



On Monday, April 26, 2021, 02:00:34 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 27/04/2021 12:56 am, Steven Fook via groups.io wrote:

I don't know if anybody experienced this or documented it, but when I opened JTAlert 2.50 this morning, the callsigns window appeared like this:




Previously it displayed nice and big in all its glory, and I did not touch any settings to modify anything in the program since I installed the update a while back.
Is there anyway to get to the properties other than the gear icon that now I cannot access?

Thanks!

Steven

Steven,

That is unexpected. I'm not sure how it came to that. There have not been any similar reports.

All the settings for the Callsigns window are held in a single config file. It includes the window size, position and zoom settings. Your image shows that the previous session position and zoom settings were restored correctly, but not the window size, indicating that the config file hadn't been removed or corrupted. I'll investigate and try to reproduce the effect.

As to unlocking the size without access to the gear icon, simple, click the Callsigns window to make it the active window then press the F2 key. That will open the Options popup and you will be able to unckeck the "Size locked" checkbox (under the "Window" section of the Options), you will then be able to drag the window borders to resize.

BTW, the F2 key is standard across all the JTAlert windows for opening their Options popup.

de Laurie VK3AMA


Laurie,

I also had the same experience two days, but I used the F3 key to resize and it has not repeated.

Gary
KE5TD

Win 10 Pro
AMD ryzen 7 16GB


locked Re: Callsigns window appeared too small to be usable and readjusted

HamApps Support (VK3AMA)
 

On 27/04/2021 12:56 am, Steven Fook via groups.io wrote:

I don't know if anybody experienced this or documented it, but when I opened JTAlert 2.50 this morning, the callsigns window appeared like this:




Previously it displayed nice and big in all its glory, and I did not touch any settings to modify anything in the program since I installed the update a while back.
Is there anyway to get to the properties other than the gear icon that now I cannot access?

Thanks!

Steven

Steven,

That is unexpected. I'm not sure how it came to that. There have not been any similar reports.

All the settings for the Callsigns window are held in a single config file. It includes the window size, position and zoom settings. Your image shows that the previous session position and zoom settings were restored correctly, but not the window size, indicating that the config file hadn't been removed or corrupted. I'll investigate and try to reproduce the effect.

As to unlocking the size without access to the gear icon, simple, click the Callsigns window to make it the active window then press the F2 key. That will open the Options popup and you will be able to unckeck the "Size locked" checkbox (under the "Window" section of the Options), you will then be able to drag the window borders to resize.

BTW, the F2 key is standard across all the JTAlert windows for opening their Options popup.

de Laurie VK3AMA


locked Re: Callsigns window appeared too small to be usable and readjusted

Joe Subich, W4TV
 

Is there anyway to get to the properties other than the gear icon that now I cannot access?
Like any other Window ... grab the lower right corner with your mouse
and pull to the size you desire.

73,

... Joe, W4TV


On 2021-04-26 10:56 AM, Steven Fook via groups.io wrote:
Hello,
I don't know if anybody experienced this or documented it, but when I opened JTAlert 2.50 this morning, the callsigns window appeared like this:
Previously it displayed nice and big in all its glory, and I did not touch any settings to modify anything in the program since I installed the update a while back.
Is there anyway to get to the properties other than the gear icon that now I cannot access?
Thanks!
Steven


locked Callsigns window appeared too small to be usable and readjusted

Steven Fook
 

Hello,

I don't know if anybody experienced this or documented it, but when I opened JTAlert 2.50 this morning, the callsigns window appeared like this:




Previously it displayed nice and big in all its glory, and I did not touch any settings to modify anything in the program since I installed the update a while back.
Is there anyway to get to the properties other than the gear icon that now I cannot access?

Thanks!

Steven


locked Re: Q65 decodes not showing

Joe Subich, W4TV
 

I was wondering if we might see implementation like FT4 ?
That's among the changes in the version currently being vetted
by the beta test team. I'd give Laurie a week or so as he is
working a couple of other issues with that version.

73,

... Joe, W4TV


On 2021-04-26 10:57 AM, Ron W3RJW via groups.io wrote:
Laurie,
I know you have a lot on have a lot on your plate, but Q65 sub-mode has been completely approved by the ADIF committee and also accepted as MFSK mode, Q65 submode by LOTW.. It's become a rather popular mode for meteor scatter and Moon Bounce on 6 meters. Along with not showing in JTAlert 2.50.0 callsigns window, I was wondering if we might see implementation like FT4 ?
Thanks
--
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: Q65 decodes not showing

Ron W3RJW
 

Laurie,

I know you have a lot on have a lot on your plate, but Q65 sub-mode has been completely approved by the ADIF committee and also accepted as MFSK mode, Q65 submode by LOTW.. It's become a rather popular mode for meteor scatter and Moon Bounce on 6 meters. Along with not showing in JTAlert 2.50.0 callsigns window, I was wondering if we might see implementation like FT4 ?

Thanks
--
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

1741 - 1760 of 36207