Re: [wsjt-devel] r8119

[Rich - K1HTV]

I really like the change in r8119 through r8121 to move only the Rx frequency 
when double clicking on a CQ line in the Band Activity column. If this feature 
remains in future candidate releases, the number of multiple callers on the 
same frequency should be greatly reduced. Most casual ops will simply click on 
a CQ line, move the green RX marker and leave their TX frequency elsewhere in 
the passband. This should make running split the norm.a good thing. The 
result will be fewer no-decodes because of multi-caller QRM.

If desired, calling on a CQing station's exact frequency can be accomplished 
with a Control-double click on the CQ line in the Band Activity column. This 
will move both green and red markers to his frequency.  A CTRL-click on a 
frequency in the waterfall display will also move both TX and RX markers to 
that frequency.

Setting ONLY your TX frequency is easily done with a Shift-Click while pointing 
to a clear frequency in the waterfall display. This should be the first step in 
setting up for split before calling a station.

I have found that running split is really the key to completing QSOs with fewer 
repeats due to QRM from competing callers. The recent change, if retained, will 
make running split much easier for FT8 users.

73,
Rich - K1HTV
PS - Now up to 143 countries worked and 118 confirmed with FT8 with 75W or less.

= = =

From: Ed Wilson 
To: 
Subject: [wsjt-devel] r8119

I built r8119 this morning and was surprised to find that with Lock Tx=Rx 
unchecked, double-clicking on someone calling CQ (or otherwise calling another 
station) just moves the Rx frequency to that of the station calling rather than 
both the Tx and Rx frequency as before.
I have been trying to train myself to operate without the Tx=Rx box checked and 
this change kind of threw me for a loop. Is this the intended behavior for the 
future or is it a bug?
As an aside, the last few builds seem to be more effective in helping me 
achieve contacts for whatever reason...nice work!
Ed, K0KC

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8119

[Ed Wilson via wsjt-devel]

Understood Joe!
I guess I am just one of those people who likes to be on the cutting edge with 
the understanding that I might suffer wounds occasionally.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/ 

On Monday, September 25, 2017, 2:57:47 PM EDT, Joe Taylor 
 wrote:  
 
 Hi Ed, Charlie, Neil, and all,

On 9/25/2017 2:34 PM, Neil Zampella wrote:
> I just build r8120 .. and that also occurs here.
> 
> The double click on a decode does NOT switch both the Tx & Rx 
> frequencies.    There is nothing listed in the commit history that shows 
> this being changed, I was using r8118 prior and this worked as normal.

As stated here fairly often in the past: if you choose to build from the 
development branch and operate using the resulting wsjt.exe, you may get 
unexpected behavior.

In particular, the HEAD of the development branch may include 
experimental code or features that are untested or not intended to be 
used in the current version.  It may not even compile properly.

Caveat emptor.

    -- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8119

[Joe Taylor]

Hi Ed, Charlie, Neil, and all,

On 9/25/2017 2:34 PM, Neil Zampella wrote:

I just build r8120 .. and that also occurs here.

The double click on a decode does NOT switch both the Tx & Rx 
frequencies.    There is nothing listed in the commit history that shows 
this being changed, I was using r8118 prior and this worked as normal.


As stated here fairly often in the past: if you choose to build from the 
development branch and operate using the resulting wsjt.exe, you may get 
unexpected behavior.


In particular, the HEAD of the development branch may include 
experimental code or features that are untested or not intended to be 
used in the current version.  It may not even compile properly.


Caveat emptor.

-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8119

[Neil Zampella]

I just build r8120 .. and that also occurs here.

The double click on a decode does NOT switch both the Tx & Rx 
frequencies.    There is nothing listed in the commit history that shows 
this being changed, I was using r8118 prior and this worked as normal.


Neil, KN3ILZ



On 9/25/2017 9:56 AM, char...@sucklingfamily.free-online.co.uk wrote:

Hi Ed

I'm also running r8119 here.

I'm seeing the same behaviour as you I think, which doesn't seem to follow
special mouse commands.

Double clicking a CQ decode for example only moves my RX freq and leaves
TX wherever it was.

Crtrl + double click moves both TX and RX.

73

Charlie G3WDG


I built r8119 this morning and was surprised to find that with Lock Tx=Rx
unchecked, double-clicking on someone calling CQ (or otherwise calling
another station) just moves the Rx frequency to that of the station
calling rather than both the Tx and Rx frequency as before.
I have been trying to train myself to operate without the Tx=Rx box
checked and this change kind of threw me for a loop. Is this the intended
behavior for the future or is it a bug?
As an aside, the last few builds seem to be more effective in helping me
achieve contacts for whatever reason...nice work!
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel








--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8119

[charlie]

Hi Ed

I'm also running r8119 here.

I'm seeing the same behaviour as you I think, which doesn't seem to follow
special mouse commands.

Double clicking a CQ decode for example only moves my RX freq and leaves
TX wherever it was.

Crtrl + double click moves both TX and RX.

73

Charlie G3WDG

> I built r8119 this morning and was surprised to find that with Lock Tx=Rx
> unchecked, double-clicking on someone calling CQ (or otherwise calling
> another station) just moves the Rx frequency to that of the station
> calling rather than both the Tx and Rx frequency as before.
> I have been trying to train myself to operate without the Tx=Rx box
> checked and this change kind of threw me for a loop. Is this the intended
> behavior for the future or is it a bug?
> As an aside, the last few builds seem to be more effective in helping me
> achieve contacts for whatever reason...nice work!
> Ed, K0KC
> k0kc@arrl.nethttp://k0kc.us/--
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel