Re: [wsjt-devel] Experimental changes in r8125

*Sent:* Saturday, September 30, 2017 9:38 PM > *To:* wsjt-devel@lists.sourceforge.net > *Subject:* Re: [wsjt-devel] Experimental changes in r8125 > > > > Hello, Hiro-san. > > The good news is that the functionality of "Lock TX=RX" is still available > thanks to the upd

Re: [wsjt-devel] Experimental changes in r8125

Sent: Saturday, September 30, 2017 7:36 PM To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Experimental changes in r8125 On 30/09/2017 03:03, Gary McDuffie wrote: On Sep 29, 2017, at 1:10 PM, Bill Somerville <mailto:g4...@c

Re: [wsjt-devel] Experimental changes in r8125

e the same handicap either temporally or permanently. Those are need this particular option.   Hiro/ JA1LZK     From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Saturday, September 30, 2017 7:36 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Experimental chan

Re: [wsjt-devel] Experimental changes in r8125

2017 7:36 PM *To:* wsjt-devel@lists.sourceforge.net *Subject:* Re: [wsjt-devel] Experimental changes in r8125 On 30/09/2017 03:03, Gary McDuffie wrote: On Sep 29, 2017, at 1:10 PM, Bill Somerville <g4...@classdesign.com> <mailto:g4...@classdesign.com> wrote: I understand that

Re: [wsjt-devel] Experimental changes in r8125

ay be some people those have the same handicap either temporally or permanently. Those are need this particular option. Hiro/ JA1LZK From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Saturday, September 30, 2017 7:36 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [

Re: [wsjt-devel] Experimental changes in r8125

On 30/09/2017 03:03, Gary McDuffie wrote: On Sep 29, 2017, at 1:10 PM, Bill Somerville wrote: I understand that there will always be a group of users who insist that the old "Lock Tx=Rx" option is needed Bill, you seem to be under the false impression that everyone

Re: [wsjt-devel] Experimental changes in r8125

> On Sep 29, 2017, at 1:10 PM, Bill Somerville wrote: > > I understand that there will always be a group of users who insist that the > old "Lock Tx=Rx" option is needed Bill, you seem to be under the false impression that everyone wants to work split and cares about

Re: [wsjt-devel] Experimental changes in r8125

+1 73 de Sebastian, W4AS > On Sep 29, 2017, at 4:30 PM, Richard Lamont wrote: > > On 29/09/17 20:10, Bill Somerville wrote: > >> I am failing to see why most of the existing automatic behaviour when >> double-clicking decodes has to be given up just for a number of >>

Re: [wsjt-devel] Experimental changes in r8125 & 8144

Where are you getting the 8144 rc 3 at? gary ww8o On Friday, September 29, 2017 3:07 PM, AB1NJ wrote: Using 8144 here now.  I don't usually post a lot, but I feel as if I have to say something now. Concerning these changes...I really think that: 1) it is now overly

Re: [wsjt-devel] Experimental changes in r8125

On 29/09/17 20:10, Bill Somerville wrote: > I am failing to see why most of the existing automatic behaviour when > double-clicking decodes has to be given up just for a number of > operators who think that by default one's Tx offset should not be moved > when replying to a CQ or QRZ call. To be

Re: [wsjt-devel] Experimental changes in r8125 & 8144

I fully agree, Rob. It made a 2 handed operation out of a simple mouse click. At least looks like we are going to have an option! On 9/29/2017 3:06 PM, AB1NJ wrote: Using 8144 here now.  I don't usually post a lot, but I feel as if I have to say something now. Concerning these changes...I

Re: [wsjt-devel] Experimental changes in r8125

Just ran across maybe an unintended behavior - Had the "double click on calls sets TX and RX freqs" box checked and was working when double clicking on stations but when I used shift to select a frequency off of another station, everything worked great (I shift-clicked off frequency to avoid

Re: [wsjt-devel] Experimental changes in r8125

On 27/09/2017 13:47, Joe Taylor wrote: Experimental new behavior for "Lock Tx=Rx" and for clicking on waterfall and decoded text. Hi Joe, I am failing to see why most of the existing automatic behaviour when double-clicking decodes has to be given up just for a number of operators who think

Re: [wsjt-devel] Experimental changes in r8125 & 8144

Using 8144 here now.  I don't usually post a lot, but I feel as if I have to say something now. Concerning these changes...I really think that: 1) it is now overly complicated, and 2) it worked better before. I always have been one of those that never checked the LockTX=RX box, and liked the

Re: [wsjt-devel] Experimental changes in r8125

Just tested - works great running my shack PC remotely from my iPad. Jim S. N2ADV On 9/29/2017 2:01 PM, Joe Taylor wrote: After further testing in the field, the experimental changes introduced in r8125 and later will now become permanent. In r8144 I have added an option to enforce simplex

Re: [wsjt-devel] Experimental changes in r8125

Thanks, Joe!  Building 8144 now and will report back. Jim S. N2ADV On 9/29/2017 2:01 PM, Joe Taylor wrote: After further testing in the field, the experimental changes introduced in r8125 and later will now become permanent. In r8144 I have added an option to enforce simplex operation (thus

Re: [wsjt-devel] Experimental changes in r8125

Hi Tim, ... I see that it says not to use “this feature” on the air in the r8120 commit comments, but does that mean we should not use any release r8120 or above on the air? Or is it something that we have to specifically do to use “RR73 NOW” and “NIL NOW”, like enter those into Tx 4

Re: [wsjt-devel] Experimental changes in r8125

After further testing in the field, the experimental changes introduced in r8125 and later will now become permanent. In r8144 I have added an option to enforce simplex operation (thus moving both Tx and Rx frequency) when you double-click a decoded text line. This option allows simpler

Re: [wsjt-devel] Experimental changes in r8125

I just deleted the draft email I was composing literally just now about this exact subject - I tend to operate remotely (99% of the time)  While a lot of that is done using a small laptop, I also use my iPad to remotely control my home machine which gets me on the air otherwise I would hardly

Re: [wsjt-devel] Experimental changes in r8125

On 9/29/2017 10:39 AM, George J Molnar wrote: One point about using control-clicks that hasn’t been raised, but might affect usability is the growing number of tablet and other touch screens in use. Double clicking for setting both RX/TX, unless TX Lock is on, is the simplest, most natural

Re: [wsjt-devel] Experimental changes in r8125

I just deleted the draft email I was composing literally just now about this exact subject - I tend to operate remotely (99% of the time)  While a lot of that is done using a small laptop, I also use my iPad to remotely control my home machine which gets me on the air otherwise I would hardly

Re: [wsjt-devel] Experimental changes in r8125

One point about using control-clicks that hasn’t been raised, but might affect usability is the growing number of tablet and other touch screens in use. Double clicking for setting both RX/TX, unless TX Lock is on, is the simplest, most natural gesture without a keyboard. At least on my end.

Re: [wsjt-devel] Experimental changes in r8125

It seems to me that an option in the settings for 1) Transceive default (previous "normal") or 2) Split default (DXing/Contest use) might keep both camps happy. Inherently, there are differing default behaviors (and their variations, accomplished by CNTL and ALT clicks) that make sense in each

Re: [wsjt-devel] Experimental changes in r8125

Hi Joe, I love the idea of “Lock Tx Freq”. After compiling and running r8127, I found that it works as advertised on the Wide Graph. But when double clicking on Decoded Text, the behavior doesn’t seem to change regardless if “Lock Tx freq” is checked or unchecked. For example, if I double

Re: [wsjt-devel] Experimental changes in r8125

Hi Joe Just testing FT* here with r8126. Commit message says: "Tx frequency is not changed unless Ctrl is held down and Lock Tx Freq not checked" I'm finding that with Lock TX Freq checked Crtl double click on decoded CQ moves TX and RX. Is this the intended behaviour?

Re: [wsjt-devel] Experimental changes in r8125

On 28/09/2017 03:44 p.m., xx wrote: Scott, i don't like it. Normal operation is TX=RX; split is an occasional mode for most. The extra steps should be in the split mode and simplex should be default.Phil Understand, Phil. I feel exactly the same way - for me, TX=RX (simplex) is also

Re: [wsjt-devel] Experimental changes in r8125

It took a bit of a higher-than-usual concentration of caffeine for me to snap into it but after that, I have begun to really like it. Jim S. N2ADV On 9/28/2017 2:12 PM, Ron Gibson wrote: Hi Joe, I for one have adapted to the "Tx frequency is not changed unless Ctrl is held down" just fine!

Re: [wsjt-devel] Experimental changes in r8125

Suggested behavior for double click might be to set TX/RX to same tone, unless lock TX is set, in which case only RX moves. Seems more intuitive and consistent. George J Molnar, CEM, CHPP KF2T - Nevada, USA > On Sep 28, 2017, at 2:12 PM, Ron Gibson wrote: > > Hi Joe, > I

Re: [wsjt-devel] Experimental changes in r8125

Hi Joe, I for one have adapted to the "Tx frequency is not changed unless Ctrl is held down" just fine! 73 de Ron VE3CGR / CG3CGR On 9/27/2017 8:47 AM, Joe Taylor wrote: Hi all, If you are building WSJT-X from code in the development branch and experimenting with it on the air, please pay