Date   

locked Thank You Laurie! Ver 2.50.0

Jim - N4ST
 

I have been with JTAlert since the beginning and it just keeps getting better!

Ver 2.50.0  brings so many new features and am enjoying it immensely.

I am having to rethink my desktop layout with all of the new window arrangements.

Great job!

 

___________

73,

Jim – N4ST

 


--
____________________
73,
Jim - N4ST


locked Re: 2.50 Like It

Michael Black
 

Right-click the gear icon and see if you have "Window size locked" checked.

Mike W9MDB




On Wednesday, April 14, 2021, 07:55:47 AM CDT, Tim N3XX <n3xx@...> wrote:


Will there be any way to resize the JTAlert window?  It doesn't require
as much horizontal space now that decoded callsigns are no longer
displayed in that window.  I would like to make it smaller left to
right, so that it will take up less space.

Thanks --- 73,
Tim - N3XX

On 2021-04-13 7:54 PM, HamApps Support (VK3AMA) wrote:
> On 13/04/2021 1:43 pm, Jon KM8V wrote:
>> Personally, I'd love to ditch the "main" window for the callsigns
>> window, if there was a way to get to the menu from there.
>
> That's coming. Not immediately, the remaining components of the main
> JTAlert window, Logging fields, the Confirmed Bands/Mode display as well
> as some miscellaneous popups need to be migrated over to the new code base.
>
> Eventually, there will be no main JTAlert window, just an icon in the
> Windows notification area or perhaps a small floating toolbar. I haven't
> decided yet, but I am leaning towards a small toolbar, or perhaps a
> choice between the two. I'm big on allowing user choice, hi.
>
> de Laurie VK3AMA
>
>






locked Re: 2.50 Like It

Tim N3XX
 

Will there be any way to resize the JTAlert window? It doesn't require as much horizontal space now that decoded callsigns are no longer displayed in that window. I would like to make it smaller left to right, so that it will take up less space.

Thanks --- 73,
Tim - N3XX

On 2021-04-13 7:54 PM, HamApps Support (VK3AMA) wrote:
On 13/04/2021 1:43 pm, Jon KM8V wrote:
Personally, I'd love to ditch the "main" window for the callsigns window, if there was a way to get to the menu from there.
That's coming. Not immediately, the remaining components of the main JTAlert window, Logging fields, the Confirmed Bands/Mode display as well as some miscellaneous popups need to be migrated over to the new code base.
Eventually, there will be no main JTAlert window, just an icon in the Windows notification area or perhaps a small floating toolbar. I haven't decided yet, but I am leaning towards a small toolbar, or perhaps a choice between the two. I'm big on allowing user choice, hi.
de Laurie VK3AMA


locked Re: Call Sign Display

Michael Black
 

It's already in the current release.  2.50.0

I take it you don't have that version?

Mike W9MDB







On Wednesday, April 14, 2021, 07:11:01 AM CDT, Tim Davis KJ4DHF via groups.io <kj4dhf@...> wrote:


Hello Laurie,

Is there a chance to make the call sign display with more than 36 on next release.  4x9 not enough anymore with JT modes picking up more users. Maybe a 6 x 10. I am steady decoding 40+ per sequence.

Thanks
Tim


locked Call Sign Display

Tim Davis KJ4DHF
 

Hello Laurie,

Is there a chance to make the call sign display with more than 36 on next release.  4x9 not enough anymore with JT modes picking up more users. Maybe a 6 x 10. I am steady decoding 40+ per sequence.

Thanks
Tim


locked Re: Transmit frequency

Ernie Barnhart
 

Laurie,

Thank you for your comments.

I thought in earlier versions when ctrl-clicking a callsign in JTAlert that  it passed that key combination on to WSJT-X that changed the transmit frequency to the receive frequency. The new version only appears to be passing the click key (not ctrl combination) to WSJT-X.

Thank you again for all you do. 

de Ernie N8DVE


locked 2.50.0 not logging propagation data

Ron W3RJW
 

Laurie
2.50.0 not logging propagation data ... Item is ticked in "Logging" options.  Has been working in previous versions.

TNX
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.3.0, JTAlert 2.50.0, HRD Deluxe v6.7
FTdx-3000, SignaLink USB


locked Re: JTAlert Will Not Install

Ed Wilson
 

Thanks for the link, Laurie!

Well, I downloaded the software and ran it and got the message:

"This app cannot run on  your PC".

I am running 32-bit Windows 10 updated to the most recent version. Do you have any clue as to why I am having this problem?

Ed, K0KC


locked Re: My Errors with JTAlert 2.50 32 bit Windows 10 PC

Bill Rogers
 

I have seen exactly that on my one 32-bit PC with windows 10 pro. All my 64-bit machines are running fine. 

Bill K2TER


On Apr 13, 2021, at 8:52 PM, William Wagaman <n3gty@...> wrote:


Hello Bill here N3GTY has anyone had this error with the new version of JTAlert:
I have 2 computers the 64bit PC windows 10 no issues ... but the errors below are on my 32bit machine. 32 Bit system because it is an older dual core with 4gb ram also windows 10 Any suggestion would be appreciated. Thanks in advance Bill

Unable to execute file:
C:\Program Files\HamApps\JTAlert\pulginsX\FrameworkChecke.exe
 
CreateProcess Failed; code 216
This version of %1 is not compatible with the version of 
Windows your're running. Check your computer's system
information and then contact the software publisher.

I get this when it is checking the Dot Net Version
I get this error when attempting to run JTAlert

<error.jpg>
 


locked JT Alert V2.5 is Awesome - many thanks

David Burden
 

Hi Laurie,

Thanks so much for your efforts on JT Alert, the changes in 2.5 are simply fantastic and the speed is amazing.

Thanks for all you do for us digital devotees.

David
VK3BDX


locked Re: icon messaging #FT8

f8nhf
 

Thank you Laurie for the quick response

you are right, for the message alert to be visible I have to increase the size of the flag to 10 at this size the window is not fluid anymore 
your idea to add a control if it is feasible or put a badge instead
 greetings

73 Denis F8NHF
 


locked Re: Callsigns not always decoding into Callsigns window.

Walt Flesher, W6SA
 

The problem seems to have resolved itself after a hard reboot of the computer after shutting everything down.  So far, so good...

Keeping my fingers crossed.

73
Walt, W6SA


locked Re: Thank You!!

Jacques F1VEV
 

Hello  agreed installed all through Win4Icomsuite latest version of WSJTX  and only HRD 6 logbook on SQL  on WIN10 no issues  grat stuff no just need to get used to new ergonomy , keep sending the mouse to the wrong part of the screen force of habit.......

Thank you Laurie 


locked Re: another dumb qusetion.... re F12

John C
 

excellent. thanks for that one Mike

 

73

John


locked Re: another dumb qusetion.... re F12

Michael Black
 

Right-click the gear icon....
Or use ALT+F4 for keyboard shortcut

Mike W9MDB





On Tuesday, April 13, 2021, 11:18:36 PM CDT, John C <vk7xx.radio@...> wrote:


OK, I pressed the F12 and enabled the 'Band Heat window'   however the only way I can close it down again is to shut down Alert. Pressinf F12 a second time does not close it...   Have I missed something ???

 

John
VK7XX


locked Re: Version 2.50.0 request

John C
 

thank you Laurie..   I did not even see this...  Adjusted and looking good.   thanks again

 

John


locked another dumb qusetion.... re F12

John C
 

OK, I pressed the F12 and enabled the 'Band Heat window'   however the only way I can close it down again is to shut down Alert. Pressinf F12 a second time does not close it...   Have I missed something ???

 

John
VK7XX


locked Re: UDP ERROR

Ed K0iL
 

I'm having the same issue after updating to latest version.  Everything stopped working.

73, de ed -K0iL


locked Update top version 1.50.0 gone wrong

Ed K0iL
 
Edited

Subject correction: Updated to version 2.50.0 gone wrong.  
Updated to JT Alert 2.50.0 and nothing works any longer.
Only the top menu line appears.  
No Sound either when testing sound.
My personal settings all seem to still be there. But it's still dead after restarting both of WSJT-X and JT Alert.
 
UDP Comm Failure error message states unable to communicate with WSJT-X process. Says see JT Alert Help for correct WSJT-X UDP Setup. That help page now recommends new UDP multicast addressing. So tried that. It still doesn't work.
 
Should I have updated WSJT-X first from 2.2.2 to latest version?
 
Anyone else having this problem with JTAlert's new version 2.50.0?
 


locked Re: 2nd instance Callsign window not following JTAlert main window on minimize - Defect Confirmed.

Gary Yarbrough, KE5TD
 



On Tuesday, April 13, 2021, 07:31:12 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 14/04/2021 5:45 am, Gary Yarbrough via groups.io wrote:
>From the settings window in the Callsign window I have ticked the box for the Callsign window to follow the JTAlert main window and it works on the 1st instance.  On the 2nd instance I also ticked the box  but the Callsign window does not minimize when I minimize the JTAlert main window. Anyone else having this issue ?

Gary / KE5TD

Gary,

Thanks for the report. I can confirm this is a defect.

I'll correct it for the next release.

de Laurie VK3AMA


Laurie,

Also the Callsign window on 2nd instance is auto closing after about 5 minutes..  The 1st instance is running normal with no issues.

Thanks for the new version I really like it !

73, Gary
KE5TD

2301 - 2320 of 36207