Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

2020-05-19 Thread Gary McDuffie
> On May 19, 2020, at 10:05, Neil Zampella wrote: > > .. someone sending an RR73 does not expect a reply, the last 73 is a > courtesy from you the answering station. I certainly do, in order to let him know I got his RR73 and he needs to sen nothing else. If I don’t send 73, I expect him

Re: [wsjt-devel] Configurations

2020-05-19 Thread Joe Taylor
Hi Ed, On 5/19/2020 8:49 PM, j...@comcast.net N4II wrote: Exactly. The difficulty is, at present there's no way for the new user to know what you've just written -- other than by receiving an email from you, or one of the other cognoscenti -- since it's not documented anywhere. (I learned abo

Re: [wsjt-devel] Configurations

2020-05-19 Thread jan0
Joe, Exactly. The difficulty is, at present there's no way for the new user to know what you've just written -- other than by receiving an email from you, or one of the other cognoscenti -- since it's not documented anywhere. (I learned about Configuration operation from a WSJT-X beta tester --

Re: [wsjt-devel] Configurations

2020-05-19 Thread Al
"*One feature I never understood is the "Clone Into" " Me neither... But it would make more sense to me if it allowed entering a new name thus  "Clone" and "Rename" in one step ( "Clone to new name" ). Sort of like "create new using existing settings". AL, K0VM * On 5/19/2020 6:30 PM, Hasan a

Re: [wsjt-devel] Configurations

2020-05-19 Thread Hasan al-Basri
I use configurations for every mode as well as DXpeditions. They work great. *One feature I never understood is the "Clone Into"* I guessed that it might be a simultaneous Clone and Rename, but I've never used it. The way I make new configurations is to start from a known perfectly working confi

Re: [wsjt-devel] Configurations

2020-05-19 Thread Joe Taylor
Hi Ed, Thanks for your comments, they are much appreciated. A few comments inline below. On 5/19/2020 4:59 PM, j...@comcast.net N4II wrote: I sense a bit of, er, annoyance on behalf of WSJT-X developers with the fact that relatively few users seem to be using Configurations -- at least, the

[wsjt-devel] Configurations

2020-05-19 Thread jan0
I sense a bit of, er, annoyance on behalf of WSJT-X developers with the fact that relatively few users seem to be using Configurations -- at least, the solution proposed to a fair number of user interface issues raised here recently seems to be the same: "Use Configurations". When I first used th

Re: [wsjt-devel] 2.2.0 rc1 - Allow Tx Frequency Changes While Transmitting

2020-05-19 Thread Joe Taylor
Steve -- On 5/19/2020 4:23 PM, Stephen VK3SIR wrote: Are changes to the frequency of any audio stream than can be adjusted through the "Audio Tx Widget" also blocked during a Tx cycle? As you could easily discover for yourself, such changes are not allowed during a transmission unless "Allo

Re: [wsjt-devel] 2.2.0 rc1 - Allow Tx Frequency Changes While Transmitting

2020-05-19 Thread Stephen VK3SIR
Joe, Thanks for the clarification. Also thanks for the notification for us all in posts to others that rc2 is imminent. Thanks also for the reminder to everyone participating that we should head to the documentation before posting. I was aware of the documentation having been there first befor

Re: [wsjt-devel] Hold TX Frequency Default

2020-05-19 Thread Reino Talarmo
>From: Jim Brown [mailto:k...@audiosystemsgroup.com] Sent: 19. toukokuuta 2020 20:25 >On 5/19/2020 6:35 AM, Joe Taylor wrote: >> I operate on 6m a lot, using FT8, MSK144, and recently also FT4. I > >never have the problem you describe. >Can you please tell me how your setup prevents the proble

Re: [wsjt-devel] Incorrect decodes

2020-05-19 Thread Reino Talarmo
The third line is an EU VHF report message with target call, sender's call, both hashed and not know in your decoder, report with serial number and six digit locator. Well, it is a false positive in any case. 73, Reino OH3mA From: K2DBK-WSJT [mailto:k2dbk+w...@k2dbk.com] Sent: 18. toukokuuta

Re: [wsjt-devel] Hold TX Frequency Default

2020-05-19 Thread Jim Brown
On 5/19/2020 6:35 AM, Joe Taylor wrote: I operate on 6m a lot, using FT8, MSK144, and recently also FT4.  I never have the problem you describe. Can you please tell me how your setup prevents the problem I've described? Is there a reason that you cannot change the behavior I've described? 7

Re: [wsjt-devel] wsjt-devel Digest, Vol 75, Issue 95

2020-05-19 Thread Al Pawlowski
If so, maybe WSJTx should only do the tx5 message atuomatically when it is not set to the default . Al Pawlowski, K6AVP Los Osos, CA USA > On May 19, 2020, at 09:11, wsjt-devel-requ...@lists.sourceforge.net wrote: > > Date: Tue, 19 May 2020 12:05:27 -0400 > From: Neil Zampella mailto:ne...@t

Re: [wsjt-devel] wsjt-devel Digest, Vol 75, Issue 94

2020-05-19 Thread Al Pawlowski
Would it not be good if double clicking any received message sent the next sequenced message? What I do (pretty automatically) now when I get to the end of a QSO cycle is select RR73, or 73 (as appropriate), enable tx and wait with my mouse cursor over the disable tx button to kill a second end

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

2020-05-19 Thread Black Michael via wsjt-devel
Yeah, I know, but a good number do it anyways... Mike On Tuesday, May 19, 2020, 11:09:47 AM CDT, Neil Zampella wrote: FWIW .. someone sending an RR73 does not expect a reply, the last 73 is a courtesy from you the answering station.    If someone keeps sending RR73, they don't un

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

2020-05-19 Thread Neil Zampella
FWIW .. someone sending an RR73 does not expect a reply, the last 73 is a courtesy from you the answering station.    If someone keeps sending RR73, they don't understand the use of that response. Neil, KN3ILZ On 5/19/2020 10:06 AM, Black Michael wrote: What he's describing has happened to me n

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

2020-05-19 Thread Black Michael via wsjt-devel
What he's describing has happened to me numerous times... You send 73 and move on to another QSO...then the last QSO sends RR73 again so you have to double-click it. Seems to me double-clicking an RR73 that has your callsign in it should automatically go to Tx 5 instead of TX3. de Mike W9MDB

Re: [wsjt-devel] Clicking on RR73 produced wrong TX response msg

2020-05-19 Thread Joe Taylor
Hi Rich, On 5/18/2020 20:16, Rich Zwirko - K1HTV wrote: *Using 2.2.0-rc1, when completing an FT8 QSO and an RR73 is received I send a 73. However if the station doesn't receive my '73' message, he re-sends his TX4 RR73 message. When I double click on his first RR73 line, instead of sending me

Re: [wsjt-devel] 2.2.0 rc1 - Allow Tx Frequency Changes While Transmitting

2020-05-19 Thread Joe Taylor
Steve -- On 5/19/2020 00:15, Stephen VK3SIR wrote: Does the "Allow Tx Frequency Changes While Transmitting" (File/Settings/General Tab) when not-checked function as intended? Yes. When this option is not checked, frequency-changing CAT commands will not be sent to your radio. My expecta

Re: [wsjt-devel] Hold TX Frequency Default

2020-05-19 Thread Joe Taylor
Hi Jim, On 5/19/2020 01:20, Jim Brown K9YC wrote: I have made this "feature request before, and hoped to see it in this beta, but it's missing. My request is that either 1) WSJT-X remember my setting of Hold TX Frequency or 2) make Hold TX Frequency the default. I am continually bitten by thi

Re: [wsjt-devel] 2.2.0 rc1 - Allow Tx Frequency Changes While Transmitting

2020-05-19 Thread Bill Somerville
On 19/05/2020 05:15, Stephen VK3SIR wrote: Hi Folks, Does the "Allow Tx Frequency Changes While Transmitting" (File/Settings/General Tab) when not-checked function as intended? My expectation would be that if disabled that any frequency changes observed in the Tx spin-box widget on the Main W

Re: [wsjt-devel] Hold TX Frequency Default

2020-05-19 Thread Peter Sumner
Hi Jim, you should consider using different configurations for the modes and try to not use the MODE selector when possible, using a Configuration for each mode will return you to exactly where you were before on that mode. I use it exclusively on the three computers here (2 are PI's) and find it