[wsjt-devel] Feature request - sticky reports

[Charles Suckling]

Hi Bill and Joe

 

Several stations have  been testing out auto-seq on QRA64 10GHz EME these
last couple of days,  with excellent results. It certainly eases the
workload, with other many other things to keep track of.

 

The subject of sticky reports has already come up.  It seems desirable (from
user feedback)  if the first decoded report could be used in all subsequent
messages in that QSO,  to avoid confusion over existing practice where the
sent report does not change as the QSO progresses.

 

We'd be grateful if you could consider this as a user selectable option for
QRA64 at some point.

 

Recent tests under very marginal conditions have once again shown the
benefits of QRA64.  It is working really well on Rex's dxpedition, and more
stations are now joining in.  We seem to have pretty much settled  on
sub-mode D for general use.  

 

73

 

Charlie

 

--
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] Trying to compile r7997

[Claude Frantz]

Hi Bill & all,

Please see the attached output of "make" which I have got while I was
trying to compile. Please help me to find what I have done wrong.

Many thanks !

Best wishes,
Claude (DJ0OT)


Here is my current environment:

Working Copy Root Path: /home/claude/ham/JoeTaylor/wsjtx
URL: svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8
Relative URL: ^/branches/wsjtx-1.8
Repository Root: svn://svn.code.sf.net/p/wsjt/wsjt
Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Revision: 7997
Node Kind: directory
Schedule: normal
Last Changed Author: bsomervi
Last Changed Rev: 7996
Last Changed Date: 2017-08-03 18:42:10 +0200 (Thu, 03 Aug 2017)

Linux 4.11.11-300.fc26.i686+PAE
cc (GCC) 7.1.1 20170622 (Red Hat 7.1.1-3)
c++ (GCC) 7.1.1 20170622 (Red Hat 7.1.1-3)
GNU Fortran (GCC) 7.1.1 20170622 (Red Hat 7.1.1-3)
GNU Make 4.2.1
License GPLv3+: GNU GPL version 3 or later

qt5-qtbase-devel-5.7.1-19.fc26.i686
[  0%] Automatic MOC for target wsjtx_udp-static
[  0%] Built target wsjtx_udp-static_autogen
[  1%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/MessageServer.cpp.o
In file included from /home/claude/ham/JoeTaylor/wsjtx/MessageServer.cpp:16:0:
/home/claude/ham/JoeTaylor/wsjtx/build/moc_MessageServer.cpp: In static member 
function ‘static void MessageServer::qt_static_metacall(QObject*, 
QMetaObject::Call, int, void**)’:
/home/claude/ham/JoeTaylor/wsjtx/build/moc_MessageServer.cpp:172:357: error: no 
matching function for call to ‘MessageServer::decode(bool&, const QString&, 
QTime&, qint32&, float&, quint32&, const QString&, const QString&)’
 case 3: _t->decode((*reinterpret_cast< 
bool(*)>(_a[1])),(*reinterpret_cast< const 
QString(*)>(_a[2])),(*reinterpret_cast< QTime(*)>(_a[3])),(*reinterpret_cast< 
qint32(*)>(_a[4])),(*reinterpret_cast< float(*)>(_a[5])),(*reinterpret_cast< 
quint32(*)>(_a[6])),(*reinterpret_cast< const 
QString(*)>(_a[7])),(*reinterpret_cast< const QString(*)>(_a[8]))); break;




 ^
In file included from /home/claude/ham/JoeTaylor/wsjtx/MessageServer.cpp:1:0:
/home/claude/ham/JoeTaylor/wsjtx/MessageServer.hpp:71:17: note: candidate: void 
MessageServer::decode(bool, const QString&, QTime, qint32, float, quint32, 
const QString&, const QString&, bool)
   Q_SIGNAL void decode (bool is_new, QString const& id, QTime time, qint32 
snr, float delta_time
 ^~
/home/claude/ham/JoeTaylor/wsjtx/MessageServer.hpp:71:17: note:   candidate 
expects 9 arguments, 8 provided
In file included from /home/claude/ham/JoeTaylor/wsjtx/MessageServer.cpp:16:0:
/home/claude/ham/JoeTaylor/wsjtx/build/moc_MessageServer.cpp:179:320: error: no 
matching function for call to ‘MessageServer::reply(const QString&, QTime&, 
qint32&, float&, quint32&, const QString&, const QString&)’
 case 10: _t->reply((*reinterpret_cast< const 
QString(*)>(_a[1])),(*reinterpret_cast< QTime(*)>(_a[2])),(*reinterpret_cast< 
qint32(*)>(_a[3])),(*reinterpret_cast< float(*)>(_a[4])),(*reinterpret_cast< 
quint32(*)>(_a[5])),(*reinterpret_cast< const 
QString(*)>(_a[6])),(*reinterpret_cast< const QString(*)>(_a[7]))); break;




^
In file included from /home/claude/ham/JoeTaylor/wsjtx/MessageServer.cpp:1:0:
/home/claude/ham/JoeTaylor/wsjtx/MessageServer.hpp:48:15: note: candidate: void 
MessageServer::reply(const QString&, QTime, qint32, float, quint32, const 
QString&, const QString&, bool)
   Q_SLOT void reply (QString const& id, QTime time, qint32 snr, float 
delta_time, quint32 delta_frequency
   ^
/home/claude/ham/JoeTaylor/wsjtx/MessageServer.hpp:48:15: note:   candidate 
expects 8 arguments, 7 provided
In file included from /home/claude/ham/JoeTaylor/wsjtx/MessageServer.cpp:16:0:
/home/claude/ham/JoeTaylor/wsjtx/build/moc_MessageServer.cpp:211:88: error: 
invalid static_cast from type ‘void (MessageServer::*)(bool, const QString&, 
QTime, qint32, float, quint32, const QString&, const QString&, bool) {aka void 
(MessageServer::*)(bool, const QString&, QTime, int, float, unsigned int, const 
QString&, const QString&, bool)}’ to type ‘_t {aka void 
(MessageServer::*)(bool, const QString&, QTime, int, float, unsigned int, const 
QString&, const QString&)}’
 if (*reinterpret_cast<_t *>(func) == 
static_cast<_t>(&MessageServer::decode)) {
  

Re: [wsjt-devel] Trying to compile r7997

[Bill Somerville]

On 04/08/2017 09:17, Claude Frantz wrote:

Please see the attached output of "make" which I have got while I was
trying to compile. Please help me to find what I have done wrong.


Hi Claude,

the compile errors are not consistent with the sources, I guess that 
something strange has happened in a build and an out of date 
dependencies is not being re-built. Try adding --clean-first to the 
build command one time.


73
Bill
G4WJS.


--
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] Trying to compile r7997

[Claude Frantz]

On 08/04/2017 01:21 PM, Bill Somerville wrote:

Hi Bill & all,

> the compile errors are not consistent with the sources, I guess that
> something strange has happened in a build and an out of date
> dependencies is not being re-built. Try adding --clean-first to the
> build command one time.

I was not successful while adding --clean-first.

I have tried to restart from an empty directory:

$ rm -rf   ~/ham/JoeTaylor/wsjtx/*
$ mkdir -p ~/ham/JoeTaylor/wsjtx/build
$ pushd ~/ham/JoeTaylor/wsjtx
$ svn checkout svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx src
$ svn switch ^/branches/wsjtx-1.8
$ svn update
$ pushd build
$ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \
-D CMAKE_INSTALL_PREFIX=~/.wsjtx ../src
$ cmake --build .
$ cmake --build . --target install

Now the compile run ended with several warnings but with the executables
installed in the install directory. But when starting, the program
announces "v1.7.1-devel r7997" and not more 1.8.0-rc2.

Where is the problem now ?

Best wishes,
Claude (DJ0OT)

--
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] Trying to compile r7997

[Bill Somerville]

On 04/08/2017 13:56, Claude Frantz wrote:

On 08/04/2017 01:21 PM, Bill Somerville wrote:

Hi Bill & all,


the compile errors are not consistent with the sources, I guess that
something strange has happened in a build and an out of date
dependencies is not being re-built. Try adding --clean-first to the
build command one time.

I was not successful while adding --clean-first.

I have tried to restart from an empty directory:

$ rm -rf   ~/ham/JoeTaylor/wsjtx/*
$ mkdir -p ~/ham/JoeTaylor/wsjtx/build
$ pushd ~/ham/JoeTaylor/wsjtx
$ svn checkoutsvn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx  src
$ svn switch ^/branches/wsjtx-1.8
$ svn update
$ pushd build
$ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \
-D CMAKE_INSTALL_PREFIX=~/.wsjtx ../src
$ cmake --build .
$ cmake --build . --target install

Now the compile run ended with several warnings but with the executables
installed in the install directory. But when starting, the program
announces "v1.7.1-devel r7997" and not more 1.8.0-rc2.

Where is the problem now ?

Best wishes,
Claude (DJ0OT)


Hi Claude,

You need to change working directory into the checked out source root 
between the 'svn co ...' and 'svn sw ...' commands.


You can save some time by checking out directly the branch you want to 
work with e.g.:


$ svn co svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8 
~/ham/JoeTaylor/wsjtx/src


No need to switch branches then.

You will get a much faster build if you have multiple cores by enabling 
parallel make using -jN where N is the number of concurrent CPU threads 
possible i.e. 2xcores for an Intel CPU with hyperthreading, like:


$ cmake --build ~/ham/JoeTaylor/wsjtx/build --target install -- -j4

for a 4 thread CPU like a dual core Core i3.

73
Bill
G4WJS.

--
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] Pulled back on 73

[James Shaver (N2ADV)]

Thanks, Bill!  I typically keep the box unchecked myself when calling CQ but I 
know there are folks who find it handy. 

Appreciate the peek!

Jim S. 
N2ADV

> On Aug 3, 2017, at 9:32 PM, Bill Somerville  wrote:
> 
>> On 04/08/2017 02:22, James Shaver (N2ADV) wrote:
>> I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he 
>> responded to me, we went through the sequence, he sent his 73 and then moved 
>> off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his TX 
>> back to where I was causing him to accidentally start calling CQ where he 
>> had just answered me. Would it be simple to have the TX not be pulled back 
>> upon receipt of the 73?  I know he could have unchecked "Call 1st" and 
>> avoided being pulled back but then if someone had answered him after calling 
>> CQ, he would have to manually answer.
> 
> Hi Jim,
> 
> I can reproduce that behaviour if I have him with "Lock Tx=Rx" checked. The 
> more use cases I test with auto-sequencing the more I am growing to dislike 
> "Lock Tx=Rx".
> 
> I will see if I can work out how to stop this sort of thing happening.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> 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] Trying to compile r7997

[Claude Frantz]

On 08/04/2017 03:11 PM, Bill Somerville wrote:

Many thanks, Bill !

Please see what happens. I'm not more sure which branch is in use now.
Where is my error now ? How can I fix it ?

Best wishes,
Claude (DJ0OT)

$ pwd
/home/claude/ham/JoeTaylor/wsjtx
$ svn co svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8
~/ham/JoeTaylor/wsjtx/src
svn: E155000: '/home/claude/ham/JoeTaylor/wsjtx/src' is already a
working copy for a different URL
$ svn info
Path: .
Working Copy Root Path: /home/claude/ham/JoeTaylor/wsjtx
URL: svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8
Relative URL: ^/branches/wsjtx-1.8
Repository Root: svn://svn.code.sf.net/p/wsjt/wsjt
Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Revision: 7997
Node Kind: directory
Schedule: normal
Last Changed Author: bsomervi
Last Changed Rev: 7996
Last Changed Date: 2017-08-03 18:42:10 +0200 (Thu, 03 Aug 2017)

$ svn update
Updating '.':
At revision 7997.


--
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] Trying to compile r7997

[Bill Somerville]

On 04/08/2017 14:32, Claude Frantz wrote:

Many thanks, Bill !

Please see what happens. I'm not more sure which branch is in use now.
Where is my error now ? How can I fix it ?

Best wishes,
Claude (DJ0OT)

$ pwd
/home/claude/ham/JoeTaylor/wsjtx
$ svn cosvn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8
~/ham/JoeTaylor/wsjtx/src
svn: E155000: '/home/claude/ham/JoeTaylor/wsjtx/src' is already a
working copy for a different URL
$ svn info
Path: .
Working Copy Root Path: /home/claude/ham/JoeTaylor/wsjtx
URL:svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8
Relative URL: ^/branches/wsjtx-1.8
Repository Root:svn://svn.code.sf.net/p/wsjt/wsjt
Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79
Revision: 7997
Node Kind: directory
Schedule: normal
Last Changed Author: bsomervi
Last Changed Rev: 7996
Last Changed Date: 2017-08-03 18:42:10 +0200 (Thu, 03 Aug 2017)

$ svn update
Updating '.':
At revision 7997.


Hi Claude,

looks like you have two source trees checked out, one at 
~/ham/JoeTaylor/wsjtx which is at ^/branches/wsjtx-1.8 and another at 
~/ham/JoeTaylor/wsjtx/src which is at ^/branches/wsjtx, you are building 
the latter.


Try this:

$ cd ~/ham/JoeTaylor/wsjtx
$ rm -r *
$ svn co svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8 src
$ mkdir build
$ cd build
$ cmake -D CMAKE_PREFIX_PATH=~/hamlib_prefix -D 
CMAKE_INSTALL_PREFIX=~/.wsjtx ../src

$ cmake --build . --target install -- -j4
$ ~/.wsjtx/bin/wsjtx

73
Bill
G4WJS.


--
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] Trying to compile r7997

[Claude Frantz]

On 08/04/2017 03:41 PM, Bill Somerville wrote:

Hi Bill & all,

Many thanks for your help. Now, I'm at 1.8.0-rc2 again.

I will try it on the air and I will continue to follow the development.

Best wishes,
Claude (DJ0OT)

> looks like you have two source trees checked out, one at
> ~/ham/JoeTaylor/wsjtx which is at ^/branches/wsjtx-1.8 and another at
> ~/ham/JoeTaylor/wsjtx/src which is at ^/branches/wsjtx, you are building
> the latter.
> 
> Try this:
> 
> $ cd ~/ham/JoeTaylor/wsjtx
> $ rm -r *
> $ svn co svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.8 src
> $ mkdir build
> $ cd build
> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib_prefix -D
> CMAKE_INSTALL_PREFIX=~/.wsjtx ../src
> $ cmake --build . --target install -- -j4
> $ ~/.wsjtx/bin/wsjtx

--
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] Worked B4 Status

[Neil Zampella]

Hi all,

this was brought up on the Facebook FT8 group, and I realized that I've 
not seen it either.It may have fallen through the cracks with the 
push to get other things done, but while I'm seeing the DXCC location 
appear, I'm not seeing any B4 status on stations that I've worked 
previously.


This may be the reason I got repeat CQ responses from a few stations 
yesterday that I had worked an hour or so previously on 40 meters.


I could be way off base on this, but ??

Neil, KN3ILZ


--
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] User Guide updates for WSJT-X Version 1.8

[Alexandre Moleiro via wsjt-devel]

Some quick notes on the user guide:

- There is no explanation about the difference between Fast, Normal and Deep 
decode in the different modes (except the notes about computing power in MSK144)
- Is the list of keyboard shortcuts on section 10.1.9 updated ?

- Just for starting could section 13.1 "Calibrating your radio" contain 
appendix C from WSPR 4.0 User doc with a few modifications?

Keep up the good work, looking good for RC273 de CT1GVN
On Wednesday, August 2, 2017, 8:43:57 PM GMT+1, Joe Taylor  
wrote:

Hi all,

In preparation for a soon-to-come second candidate release of WSJT-X 
Version 1.8, I committed a large number of updates to the WSJT-X User 
Guide today.

The new user guide is posted here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html

If you are using one of the pre-release versions of WSJT-X v1.8, please:

1. Refer to the User Guide first, whenever you have questions. It's only 
a single *F1* keystroke away, if you are running WSJT-X.

2. If you find something confusing, missing, or otherwise in need of 
improvement, please post details to this list.  The User Guide can 
always be made better -- and we rely on *you* to help us do that.

    -- 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] Pulled back on 73

[Pedro Carlos Pocciotti]

Dear James,

Do not forget to set as "*checked"** the box on "TX after sending 73" on
Settings-Behavior configuration General Tab.*

73's Pedro - PY2HH



 Sent with Mailtrack


On Thu, Aug 3, 2017 at 10:22 PM, James Shaver (N2ADV) 
wrote:

> I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he
> responded to me, we went through the sequence, he sent his 73 and then
> moved off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his
> TX back to where I was causing him to accidentally start calling CQ where
> he had just answered me. Would it be simple to have the TX not be pulled
> back upon receipt of the 73?  I know he could have unchecked "Call 1st" and
> avoided being pulled back but then if someone had answered him after
> calling CQ, he would have to manually answer.
>
> Just curious. :)
>
> 73!
> Jim S.
> N2ADV
>
> 
> --
> 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
> 
>



-- 
*If you stand for nothing, you'll fall for anything.*
e-mail me (click down)
Pedro Carlos Pocciotti 
*
--
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] User Guide updates for WSJT-X Version 1.8

[Joe Taylor]

Hi Alex,

On 8/4/2017 11:02 AM, Alexandre Moleiro via wsjt-devel wrote:


- Is the list of keyboard shortcuts on section 10.1.9 updated ?


As far as I am aware, yes.  Did you find something missing or incorrect?

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

[wsjt-devel] Remove "Lock Tx=Rx" QSY 'feature'?

[Rich - K1HTV]

Bill, Jim, et al,

   As we all know,  a double click on a CQer's callsign results in both the TX 
and RX frequency changing to the CQer's frequency, even with the "Lock Tx=Rx" 
unchecked. However, with the box unchecked, if a user clicks on a different 
frequency to call CQ, only the RX frequency and the green bracket change. To 
change the TX frequency one must hold the 'Shift' key... but then only the 
TX frequency and the red bracket change. Not many know that to move both TX & 
RX freqs requires holding the "Ctrl"key down while clicking on the desired 
TX/RX frequency. That is why most folks keep the TX=RX box checked, because it 
is easier. But as Jim mentioned, doing so pulls the station you just worked 
back to your frequency, resulting in possible QRM to you.


Maybe the answer with FT8 would be to remove the feature of pulling the other 
station to your frequency and have him stay on his original TX frequency. A 
good reason for him to stay there is because:

1) You were copying him well there.

2) In all likelihood, he was copying you better on your frequency rather that 
through multiple callers on his own frequency.


I can see that with modes where a narrow 'Tol' is used that the calling station 
to be on or very near to your TX frequency. But with FT8, where almost all 
users want the the entire frequency range decoded,  I don't think that it is 
desirable to have a calling station moved away from his original operating 
frequency to a different one simply because he had the "Locked Tx=Rx" box 
checked. What is gained by this?


If the box was completely eliminated then double clicking on a call sign would 
move the TX & RX freqs to the CQer's frequency. After this is done, those who 
want to call off frequency can use one of a number of available keyboard 
shortcuts.


73,

Rich - K1HTV


= = =


On 04/08/2017 02:22, James Shaver (N2ADV) wrote:

I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he 
responded to me, we went through the sequence, he sent his 73 and then moved 
off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his TX back 
to where I was causing him to accidentally start calling CQ where he had …


Hi Jim,

I can reproduce that behaviour if I have him with "Lock Tx=Rx" checked.
The more use cases I test with auto-sequencing the more I am growing to
dislike "Lock Tx=Rx".

I will see if I can work out how to stop this sort of thing happening.

73
Bill
G4WJS.
--
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] FT8 "Tx Even/1st" label ambiguity

[Rich - K1HTV]

On the FT8 screen, there is an ambiguity as to meaning "Tx even/1st". A number 
of folks new to the mode have expressed some confusion as to their meanings. 


With 15 second sequencing, "Tx even" can be interpreted as meaning transmit on 
the even sequences, that is, the 2nd and 4th 15 second sequence.


With 15 second sequencing, "1st" can be interpreted as transmit on the first, 
and subsequently, on the 3rd sequence.


The two meanings, as related to 15 second sequencing, are at odds.


Why not, for the FT8 screen, change that check box definition to:

"1st & 3rd 15 second sequence" or an abbreviated "1st & 3rd 15 sec seq" ?


73,

Rich - K1HTV--
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] Feature request - sticky reports

[Gary McDuffie]

> On Aug 4, 2017, at 1:37 AM, Charles Suckling 
>  wrote:
> 
> The subject of sticky reports has already come up.  It seems desirable (from 
> user feedback)  if the first decoded report could be used in all subsequent 
> messages in that QSO,  to avoid confusion over existing practice where the 
> sent report does not change as the QSO progresses.

I’m not involved in EME, but I’ve often wished that when the signal report is 
given more than once, it would send the highest report to that point.  In other 
words, if the signal went from -12 to -10 before it was acknowledged, the -10 
would be the official report and put in the log that way.  This could be the 
case for all modes, I assume.  I don’t know if this would cause a problem, but 
I thought I would mention it in relation to your post.

Gary - AG0N
--
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] FT8 "Tx Even/1st" label ambiguity

[Bill Somerville]

On 04/08/2017 18:52, Rich - K1HTV wrote:


On the FT8 screen, there is an ambiguity as to meaning "Tx even/1st". 
A number of folks new to the mode have expressed some confusion as to 
their meanings.




Hi Rich,

I don't understand. 0 and 30 are even numbers, 15 and 45 are odd. If 
anything the 60s T/R periods should cause confusion, but there minutes 
1, 3, 5, ... are odd, minutes 0, 2, 4, 6, ... are even.


Time uses zero based indexing (well apart from months but they are 
strange in all respects!), so the 15s T/R periods are the zeroth, first, 
second, third.


73
Bill
G4WJS.

--
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] WSJT-X: development branch has double line spacing of decodeds

[Bill Somerville]

Hi All,

I am aware I have broken the decode prints in WSJT-X on the development 
branch. I did some re-working on Linux to improve memory usage where it 
works just fine. I will get Windows sorted out soon and check macOS.


Sorry for any disruption.

73
Bill
G4WJS.


--
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] Worked B4 Status

[Neil Zampella]

URP .. nevermind .. just looked at the code.

Neil, KN3ILZ


On 8/4/2017 11:37 AM, Neil Zampella wrote:

Hi all,

this was brought up on the Facebook FT8 group, and I realized that 
I've not seen it either.It may have fallen through the cracks with 
the push to get other things done, but while I'm seeing the DXCC 
location appear, I'm not seeing any B4 status on stations that I've 
worked previously.


This may be the reason I got repeat CQ responses from a few stations 
yesterday that I had worked an hour or so previously on 40 meters.


I could be way off base on this, but ??

Neil, KN3ILZ






--
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] Suggestion

[Bill Turner via wsjt-devel]

Would it be useful to add the revision version to the top line on the main 
screen? something like:
WSJT-X v1.7.1-devel-r7997 by K1JT
When you have a couple versions on the computer, it would help to know you are 
using the right one.
Thanks to all the development team folks who have helped me get FT8 playing 
well. 24 states and 12 countries so far.
Bill Turner, W4WNT



--
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] Suggestion

[Joe Taylor]

On 8/4/2017 2:46 PM, Bill Turner via wsjt-devel wrote:
Would it be useful to add the revision version to the top line on the 
main screen? something like:


WSJT-X v1.7.1-devel-r7997 by K1JT


It's on the *Help -> About" screen (Ctrl+F1).

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

[wsjt-devel] Bug report: Mouse Double-Click holding ALT key on Linux Ubuntu

[Alexandre Moleiro via wsjt-devel]

Holding down the ALT key while double clicking on a call is not working on 
Linux Ubuntu 16.04.Holding the ALT key seems to be reserved for accessing the 
menus with the keyboard and even a single click will be disregarded while 
holding ALT
73 de CT1GVN
--
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] Blank lines in Band Activity

[Alessandro Gorobey via wsjt-devel]

Problably is my error, but I update JTSDK, and svn to r 7999
there is blank lines in Band Activity window.
Happend to others ???
ALL.TXT seem correct


 20m
184600  -1 -0.5  890 ~  PA3EEG SV5AZK +08

184600 -19  0.6  988 ~  ON7AN LZ5RO -14

184600  -4 -0.3 1522 ~  CQ DX LZ2HA KN33 ~Bulgaria
 20m
184615 -12  0.1 1792 ~  MX0SKR RW4LMR RRR

 20m
184630   5 -0.5 1037 ~  PA3EEG SV5AZK RRR

184630  -4 -0.3 1522 ~  CQ DX LZ2HA KN33 ~Bulgaria
 20m
184645 -15  0.1 1792 ~  MX0SKR RW4LMR 73

 20m
184700   6  0.1 1184 ~  PA3EEG SV5AZK 73

184700  -3 -0.3 1522 ~  CQ DX LZ2HA KN33 ~Bulgaria
 20m
184715 -19  0.6 1945 ~  ON8BB YU1RH -11

 20m
184730  -3  0.1 1184 ~  CQ SV5AZK KM46 !Dodecanese
184730  -5 -0.3 1522 ~  CQ DX LZ2HA KN33 ~Bulgaria
 20m
184745 -20  0.1 1581 ~  OZ1FHU EK6RSC RRR

 20m
184800   2  0.0 1184 ~  CQ SV5AZK KM46 !Dodecanese
 20m
184815 -20  0.6 1944 ~  ON8BB YU1RH RRR

 20m
184830 -20  0.1  470 ~  CQ LZ5RO KN12 ~Bulgaria
184830   5 -0.0 1188 ~  DH2LAB SV5AZK -16

184830  -5 -0.3 1522 ~  CQ DX LZ2HA KN33 ~Bulgaria
184830 -16  0.7 1688 ~  3W3B EA8ARI IL18

 20m
184900 -19  0.1  470 ~  CQ LZ5RO KN12 ~Bulgaria
184900   7 -0.0 1188 ~  DH2LAB SV5AZK -16

184900 -10 -0.3 1522 ~  CQ DX LZ2HA KN33 ~Bulgaria
184900 -15  0.7 1687 ~  3W3B EA8ARI IL18

73
Sandro
IW3RAB

--
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] User Guide updates for WSJT-X Version 1.8

[Alexandre Moleiro via wsjt-devel]

Hi Joe, the user guide is OK.
After rechecking I think I found a bug maybe specific to Linux Ubuntu, every 
keyboard shortcut works but CTRL-E for enabling TX Even/1st stops working after 
a single click on the Band activity or RX frequency windows, it starts working 
again after clicking on one of the buttons.

73 de CT1GVN


On Friday, August 4, 2017, 6:20:50 PM GMT+1, Joe Taylor  
wrote:

Hi Alex,

On 8/4/2017 11:02 AM, Alexandre Moleiro via wsjt-devel wrote:

> - Is the list of keyboard shortcuts on section 10.1.9 updated ?

As far as I am aware, yes.  Did you find something missing or incorrect?

    -- 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] WSJT-X: development branch has double line spacing of decodeds

[Alessandro Gorobey via wsjt-devel]

Sorry,

Il 04/08/2017 21:17, Wolfgang ha scritto:

Hello Alessandro,


did you read this message, before you wrote yours ? ;-)


73 de Wolfgang
OE1MWW


Friday, August 4, 2017, 8:20:08 PM, Bill wrote:

Re: [wsjt-devel] WSJT-X: development branch has double line spacing of decodeds


Hi All,



I am aware I have broken the decode prints in WSJT-X on the development
branch. I did some re-working on Linux to improve memory usage where it
works just fine. I will get Windows sorted out soon and check macOS.



Sorry for any disruption.



73
Bill
G4WJS.



--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!



--
73
Sandro
IW3RAB

--
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] FT8 "Tx Even/1st" label ambiguity

[Rich - K1HTV]

Bill,

There is no confusion as to what are considered even and odd minute numbers. 
But as long as I have been doing meteor scatter (since the mid 60's),  here in 
the States, for 15 second sequence M/S schedules,  we have always considered 
each minute to be broken into  4 sequences.  The first and third 15 second 
periods are called  ODD  and the 2nd and 4th periods are called EVEN.


Your way of reasoning 'even' and 'odd', when referring to 15 second periods, 
assumes that the even periods begin at the 00, 15, 30 & 45 second marks. Others 
may reason that the first period starts at second number 01 and not second 
number 00.  Have European meteor scatter enthusiasts always considered the 
first 15 second period of each minute to be odd or even?  


I believe that my suggestion of changing the present FT8 screen's  "Tx 
even/1st"  description to "1st & 3rd 15 second sequence" or an abbreviated 
version of "1st & 3rd 15 sec seq"  will make the meaning of the check box very 
clear as to eliminate the present ambiguity.


73,

Rich - K1HTV


= = =


Date: Fri, 4 Aug 2017 18:59:40 +0100
From: Bill Somerville mailto:g4...@classdesign.com >
To: wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] FT8 "Tx Even/1st" label ambiguity
Message-ID: <15936bbf-e02c-0491-420c-19b944bf1...@classdesign.com 
mailto:15936bbf-e02c-0491-420c-19b944bf1...@classdesign.com >
Content-Type: text/plain; charset="utf-8"; Format="flowed"

On 04/08/2017 18:52, Rich - K1HTV wrote:

> On the FT8 screen, there is an ambiguity as to meaning "Tx even/1st".
> A number of folks new to the mode have expressed some confusion as to
> their meanings.
> 

Hi Rich,

I don't understand. 0 and 30 are even numbers, 15 and 45 are odd. If
anything the 60s T/R periods should cause confusion, but there minutes
1, 3, 5, ... are odd, minutes 0, 2, 4, 6, ... are even.

Time uses zero based indexing (well apart from months but they are
strange in all respects!), so the 15s T/R periods are the zeroth, first,
second, third.

73
Bill
G4WJS.
--
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] FT8 "Tx Even/1st" label ambiguity

[Joe Taylor]

Hi Rich,

K1HTV wrote:
I believe that my suggestion of changing the present FT8 screen's  "Tx 
even/1st"  description to "1st & 3rd 15 second sequence" or an 
abbreviated version of "1st & 3rd 15 sec seq"  will make the meaning of 
the check box very clear as to eliminate the present ambiguity.


WSKJT-X supports many different operating modes.  Some of the modes 
support more than one sequence length.


The User Guide is perfectly clear about what "Tx even/1st" means:

"Check Tx even to transmit in even-numbered UTC minutes or sequences, 
starting at 0. Uncheck this box to transmit in the odd sequences."


Essentially the same definition appears in the "Tool Tip" displayed when 
you hover the mouse over this checkbox.


These simple statements are not ambiguous, and thousands of WSJT and 
WSJT-X users seem to have found them understandable.


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

Re: [wsjt-devel] FT8 "Tx Even/1st" label ambiguity

[Gary McDuffie]

> On Aug 4, 2017, at 2:08 PM, Rich - K1HTV  wrote:
> 
> Your way of reasoning 'even' and 'odd', when referring to 15 second periods, 
> assumes that the even periods begin at the 00, 15, 30 & 45 second marks. 
> Others may reason that the first period starts at second number 01 and not 
> second number 00.  Have European meteor scatter enthusiasts always considered 
> the first 15 second period of each minute to be odd or even? 


Admittedly, I am new to the game, having only been in this leg of digital for a 
few years, but even before that, 1st/EVEN meant he who transmits in the first 
sequence of the EVEN minute.  The is used throughout the modes, which, by the 
way, don’t limit themselves to 15, 30 and 60 second sequences.  The fast modes 
have 5, 10, 15, and 30 second sequences.  I’ve never seen any confusion over 
what is 1st/even vs 2nd/odd.

However, I’m curious if this discussion might answer why I see JA calling CQ US 
on ODD sequence, and I understand that at least some EU stations operating the 
same way, transmitting to us on EVEN.

I’ve never seen this discussion before, but have been on digital since the 
early 80s.

Gary - AG0N
--
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] FT8 "Tx Even/1st" label ambiguity

[Joe]

Just watching the program.
Even ON ( Checked) The program transmits from 00 to 15, rec 15 to 30 
transmits 30 to 45, recv 45 to 00.


Odd just flips them all.

Joe WB9SBD
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
On 8/4/2017 6:03 PM, Gary McDuffie wrote:

On Aug 4, 2017, at 2:08 PM, Rich - K1HTV  wrote:

Your way of reasoning 'even' and 'odd', when referring to 15 second periods, 
assumes that the even periods begin at the 00, 15, 30 & 45 second marks. Others 
may reason that the first period starts at second number 01 and not second number 
00.  Have European meteor scatter enthusiasts always considered the first 15 second 
period of each minute to be odd or even?


Admittedly, I am new to the game, having only been in this leg of digital for a 
few years, but even before that, 1st/EVEN meant he who transmits in the first 
sequence of the EVEN minute.  The is used throughout the modes, which, by the 
way, don’t limit themselves to 15, 30 and 60 second sequences.  The fast modes 
have 5, 10, 15, and 30 second sequences.  I’ve never seen any confusion over 
what is 1st/even vs 2nd/odd.

However, I’m curious if this discussion might answer why I see JA calling CQ US 
on ODD sequence, and I understand that at least some EU stations operating the 
same way, transmitting to us on EVEN.

I’ve never seen this discussion before, but have been on digital since the 
early 80s.

Gary - AG0N
--
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] Scroll patch

[Black Michael via wsjt-devel]

Disable auto scrolling while DisplayText widget has focus.
https://www.dropbox.com/s/awnfq5yimshccuo/scroll.patch?dl=1


de Mike W9MDB
--
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