Re: [wsjt-devel] Misleading QTH info on JTAlert

2024-02-15 Thread Reino Talarmo via wsjt-devel
: Luis Miguel Castañeda via wsjt-devel [mailto:wsjt- > de...@lists.sourceforge.net] > Sent: Thursday, February 15, 2024 12:00 PM > To: WSJT software development de...@lists.sourceforge.net> > Cc: Luis Miguel Castañeda > ; vk3a...@vkdxer.net > Subject: Re: [wsjt-devel] Misleading QT

Re: [wsjt-devel] Misleading QTH info on JTAlert

2024-02-15 Thread Luis Miguel Castañeda via wsjt-devel
I have the exact same problem, I operate from IM89AW and IN70HD with same callsign. I haven't had complains, but saw the issue. On Tuesday, February 13 2024, 10:29:02, Ed Stokes via wsjt-devel wrote: 1. ( ) text/plain (*) text/html Laurie & Uwe, As a ham who operates from

[wsjt-devel] Misleading QTH info on JTAlert

2024-02-13 Thread Ed Stokes via wsjt-devel
Laurie & Uwe, As a ham who operates from several locations using the same call sign but different grid squares (FN33 & DM04), it often happens that other ops will be misdirected by JTAlert, leading them to believe they have contacted Vermont (FN33) when they have responded to my call clearly

[wsjt-devel] Misleading QTH info on JTAlert

2024-02-13 Thread Ed Stokes via wsjt-devel
Laurie & Uwe, As a ham who operates from several locations using the same call sign but different grid squares (FN33 & DM04), it often happens that other ops will be misdirected by JTAlert, leading them to believe they have contacted Vermont (FN33) when they have responded to my call clearly