Re: [wsjt-devel] Double-click Band Activity responses

[Rich - K1HTV]

Joe,
  I downloaded and was using r8134 this afternoon and it works fine, as 
described, with no problems. I really like your idea of replacing the Tx=Rx 
with the 'Lock Tx Freq' option. If this option is included in the next release, 
the benefits of running split over simplex operation should be strongly 
emphasized in the documentation. 

I believe that the approach of a user locking his TX frequency to the quiet 
spot that he picked should greatly reduce the on-frequency pileups that are 
presently occurring. It has been frustrating to call CQ and have multiple 
callers but no decodes. One trick I have done is to Shift-click up or down 50 
to 100 Hz. Some times at least one of the callers, with their Tx=Rx checked, 
will follow me. Then I can copy at least one of the callers. 

I was on 40M this morning and around 1150Z and decoded 4S7AB in the middle of 
the band. I quickly Shift-clicked on 2200+ Hz to run split and gave him a call. 
I almost fell off my chair when he responded to my call. A quick set of 
exchanges and Sri Lanka was in the K1HTV log for FT8 DXCC country #147. I was 
running 75W to a ZS6BKW (modified G5RV) antenna at 65 ft and the K3 at 75W. He 
was on solar power and using a 2 element 40M quad. Also snagged XT2AT on 60M 
FT8 yesterday. You might want to add 5357 KHz to the FT8 frequency list, as 
that seems to be the channel that FT8 and some JT65 is being worked at least in 
NA, Europe and by the Africans that I've seen on 60M FT8.

Thanks again to you and the WSJT-X Team for all the work done to develop and 
improve the new FT8 mode.

As I've said before, FT8 is GREAT!

73,
Rich - K1HTV

= = =


> On September 28, 2017 at 11:14 AM Joe Taylor  wrote:
> 
> 
> Hi Rich,
> 
> Now that SourceForge seems to have fixed their problems, please build 
> and test WSJT-X r8131 (or later) from the development branch and let me 
> know how you like the Tx Freq behavior.
> 
>   -- 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] Experimental changes in r8125

[Tim Carlson]

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 click with Command held down 
(I’m using OS X 10.11.6), the Tx frequency jumps to the decoded frequency no 
matter the state of the check box.

One other thing seems broken - from JT-Bridge (2.2.5), double clicking a CQ 
call no longer has any effect (doesn’t cause WSJT-X to reply).  If I go back to 
1.8 rc2, even without restarting JT-Bridge, it works fine.  I cycled back 
through each revision, and had to go back to r8119 before a double-click on a 
CQ in JT-Bridge causes WSJT-X to initiate a reply.  Did something in r8120 
disable the incoming UDP messages?  

Also, 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 manually?

Thanks again for all your hard work!

-Tim Carlson (KD0GYG) 

> On Sep 28, 2017, at 4:19 PM, James Shaver  wrote:
> 
> 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!
>> 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 attention to the commit 
>>> message for r8125 and report your findings here.
>>> 
>>> For full and open disclosure I'll copy the commit message here:
>>> 
>>> ## 
>>> Experimental new behavior for "Lock Tx=Rx" and for clicking on waterfall 
>>> and decoded text.
>>> 
>>> 1. Checkbox "Lock Tx=Rx" is now labeled "Lock Tx Freq", and its meaning is 
>>> quite different.  If checked, the audio Tx frequency cannot be changed. 
>>> It's like the "Lock" function on some transceivers.
>>> 
>>> 2. Clicking on the Wide Graph waterfall and on lines of decoded text now 
>>> behave as follows:
>>> 
>>> Click on   Action
>>> -
>>> Waterfall: Click to set Rx frequency
>>>Shift-click to set Tx frequency
>>>Ctrl-click to set Rx and Tx frequencies
>>>If Lock Tx Freq is checked, Tx freq does not move
>>>Double-click to set Rx frequency and decode there
>>> 
>>> Decoded Text:  Double-click to copy transmitting callsign to DX Call
>>>and locator to DX Grid; change Rx frequency to decoded
>>>signal's frequency; generate standard messages.
>>>Tx frequency is not changed unless Ctrl is held down
>>>and Lock Tx Freq not checked.
>>> 
>>> If this experimental behavior is adopted, some descriptions in the User 
>>> Guide and Special Mouse Commands will need to be updated.
>>> 
>>> 3. Starting to implement a new function on the Tools menu, "Solve for 
>>> calibration parameters".  This is not yet finished; DO NOT USE in its 
>>> present form.
>>> ## 
>>> 
>>> -- 73, 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
> 
> -- 
> 73,
> 
> Jim S.
> N2ADV
> www.qrz.com/db/N2ADV
> https://www.facebook.com/groups/FT8.Digital.Mode/
> 
> 
> --
> 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] Experimental changes in r8125

[charlie]

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?

Charlie

> Hi all,
>
> If you are building WSJT-X from code in the development branch and
> experimenting with it on the air, please pay attention to the commit
> message for r8125 and report your findings here.
>
> For full and open disclosure I'll copy the commit message here:
>
> ##
> Experimental new behavior for "Lock Tx=Rx" and for clicking on waterfall
> and decoded text.
>
> 1. Checkbox "Lock Tx=Rx" is now labeled "Lock Tx Freq", and its meaning
> is quite different.  If checked, the audio Tx frequency cannot be
> changed. It's like the "Lock" function on some transceivers.
>
> 2. Clicking on the Wide Graph waterfall and on lines of decoded text now
> behave as follows:
>
> Click on   Action
> -
> Waterfall: Click to set Rx frequency
> Shift-click to set Tx frequency
> Ctrl-click to set Rx and Tx frequencies
> If Lock Tx Freq is checked, Tx freq does not move
> Double-click to set Rx frequency and decode there
>
> Decoded Text:  Double-click to copy transmitting callsign to DX Call
> and locator to DX Grid; change Rx frequency to decoded
> signal's frequency; generate standard messages.
> Tx frequency is not changed unless Ctrl is held down
> and Lock Tx Freq not checked.
>
> If this experimental behavior is adopted, some descriptions in the User
> Guide and Special Mouse Commands will need to be updated.
>
> 3. Starting to implement a new function on the Tools menu, "Solve for
> calibration parameters".  This is not yet finished; DO NOT USE in its
> present form.
> ##
>
>   -- 73, 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] Experimental changes in r8125

[Scott Bidstrup]

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 BY FAR the most common mode I use (rarely use split), since I'm 
neither a DX chaser nor a contester.  It's the logical mode for both 
casual users and new users that are naïve to all the subtleties of how 
to use this software casually.  But we'll see what comes of it. I'll 
pass along your comment to the development list...


...List readers: The above is from a list non-member, but who compiles 
his own latest versions, and tried this, but doesn't like it, as, like 
me, he is a casual user, and is neither DX chaser nor contester (and I 
have a suspicion that there are more users like us than are in those two 
categories).  He's told me in a previous message that he found it 
sufficiently inconvenient that he uninstalled 8133 and went back to a 
previous version that doesn't have this change.


I would suggest that if this is going to become a permanent feature, it 
should be part of a feature set that is active ONLY when a 
"contesting/DX chasing mode" tick box is checked.  Which, for Phil and 
I, it almost never will be.


Scott
TI3/W7RI


--
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] Experimental changes in r8125

[James Shaver]

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!

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 attention to the commit 
message for r8125 and report your findings here.


For full and open disclosure I'll copy the commit message here:

## 

Experimental new behavior for "Lock Tx=Rx" and for clicking on 
waterfall and decoded text.


1. Checkbox "Lock Tx=Rx" is now labeled "Lock Tx Freq", and its 
meaning is quite different.  If checked, the audio Tx frequency 
cannot be changed. It's like the "Lock" function on some transceivers.


2. Clicking on the Wide Graph waterfall and on lines of decoded text 
now behave as follows:


Click on   Action
-
Waterfall: Click to set Rx frequency
   Shift-click to set Tx frequency
   Ctrl-click to set Rx and Tx frequencies
   If Lock Tx Freq is checked, Tx freq does not move
   Double-click to set Rx frequency and decode there

Decoded Text:  Double-click to copy transmitting callsign to DX Call
   and locator to DX Grid; change Rx frequency to decoded
   signal's frequency; generate standard messages.
   Tx frequency is not changed unless Ctrl is held down
   and Lock Tx Freq not checked.

If this experimental behavior is adopted, some descriptions in the 
User Guide and Special Mouse Commands will need to be updated.


3. Starting to implement a new function on the Tools menu, "Solve for 
calibration parameters".  This is not yet finished; DO NOT USE in its 
present form.
## 



-- 73, 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


--
73,

Jim S.
N2ADV
www.qrz.com/db/N2ADV
https://www.facebook.com/groups/FT8.Digital.Mode/


--
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] Experimental changes in r8125

[George J Molnar]

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 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 attention to the commit message 
>> for r8125 and report your findings here.
>> 
>> For full and open disclosure I'll copy the commit message here:
>> 
>> ## 
>> Experimental new behavior for "Lock Tx=Rx" and for clicking on waterfall and 
>> decoded text.
>> 
>> 1. Checkbox "Lock Tx=Rx" is now labeled "Lock Tx Freq", and its meaning is 
>> quite different.  If checked, the audio Tx frequency cannot be changed. It's 
>> like the "Lock" function on some transceivers.
>> 
>> 2. Clicking on the Wide Graph waterfall and on lines of decoded text now 
>> behave as follows:
>> 
>> Click on   Action
>> -
>> Waterfall: Click to set Rx frequency
>>Shift-click to set Tx frequency
>>Ctrl-click to set Rx and Tx frequencies
>>If Lock Tx Freq is checked, Tx freq does not move
>>Double-click to set Rx frequency and decode there
>> 
>> Decoded Text:  Double-click to copy transmitting callsign to DX Call
>>and locator to DX Grid; change Rx frequency to decoded
>>signal's frequency; generate standard messages.
>>Tx frequency is not changed unless Ctrl is held down
>>and Lock Tx Freq not checked.
>> 
>> If this experimental behavior is adopted, some descriptions in the User 
>> Guide and Special Mouse Commands will need to be updated.
>> 
>> 3. Starting to implement a new function on the Tools menu, "Solve for 
>> calibration parameters".  This is not yet finished; DO NOT USE in its 
>> present form.
>> ## 
>> 
>> -- 73, 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
--
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

[wsjt-devel] Can't access svn

[Dan Malcolm]

I still can’t get an svn update from Sourceforge, even though it appears to be 
up.  If I skip updating, and run with ‘clean’ enabled, WSJT-X builds just fine, 
but remains stuck at r8123.  Prior to Sourceforge being down for a couple of 
days this worked perfectly.  Maintenance reports v0706 Release 710 and was just 
updated/upgraded this morning.
__
Dan – K4SHQ

--
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] Experimental changes in r8125

[Ron Gibson]

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 attention to the commit 
message for r8125 and report your findings here.


For full and open disclosure I'll copy the commit message here:

## 

Experimental new behavior for "Lock Tx=Rx" and for clicking on 
waterfall and decoded text.


1. Checkbox "Lock Tx=Rx" is now labeled "Lock Tx Freq", and its 
meaning is quite different.  If checked, the audio Tx frequency cannot 
be changed. It's like the "Lock" function on some transceivers.


2. Clicking on the Wide Graph waterfall and on lines of decoded text 
now behave as follows:


Click on   Action
-
Waterfall: Click to set Rx frequency
   Shift-click to set Tx frequency
   Ctrl-click to set Rx and Tx frequencies
   If Lock Tx Freq is checked, Tx freq does not move
   Double-click to set Rx frequency and decode there

Decoded Text:  Double-click to copy transmitting callsign to DX Call
   and locator to DX Grid; change Rx frequency to decoded
   signal's frequency; generate standard messages.
   Tx frequency is not changed unless Ctrl is held down
   and Lock Tx Freq not checked.

If this experimental behavior is adopted, some descriptions in the 
User Guide and Special Mouse Commands will need to be updated.


3. Starting to implement a new function on the Tools menu, "Solve for 
calibration parameters".  This is not yet finished; DO NOT USE in its 
present form.
## 



-- 73, 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