date:20200522

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread Stephen VK3SIR

Correction here: 

> I personally use DXKeeper as the central logging tool and use its "Export 
> QSO's" function to "Export standard ADIF" 
> back to the "wsjtx.log" file (found in the location accessible by "File/Open 
> Log Directory").  DXKeeper has great tools 
> for managing duplicates. When all duplicates are removed periodically write 
> them back to  WSJT-X over-writing 
> previous "wsjtx.log" instances :-)

Needs be:

I personally use DXKeeper as the central logging tool and use its "Export 
QSO's" function to "Export standard ADIF" 
back to the "wsjtx_log.adi" file (found in the location accessible by 
"File/Open Log Directory").  DXKeeper has great tools 
for managing duplicates. When all duplicates are removed periodically write 
them back to  WSJT-X over-writing 
previous "wsjtx_log.adi" instances :-)

Original message corrected:

From: Stephen VK3SIR  
Sent: Saturday, 23 May 2020 6:34 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] exporting from adi

Hi Michelle,

By far the best way to avoid duplicates in logs is to not set 
"Settings\Reporting\ Log automatically..." . If you come back with a RR73, auto 
log, and then a station comes back with a R-XX (what I term a "RR/73 Loop") 
then both communication and logging can lead to duplicates in logs.

Each logged entry should be manually approved (so do not check "Log 
automatically").

Some software loggers and bridges such as JTAlert (that I use and recommend 
heavily) also are not perfect. I use JTALert with DXLab's DXKeeper. No matter 
what I do sometimes (and erratically) a duplicate is logged to eQSL. These are 
issues for their support forums. Despite this forewarning  would strongly echo 
Jim's post and recommend JTAlert's use to you !

JTAlert can be found at  https://hamapps.com. DXLab can be found at 
https://dxlabsuite.com . None of these products are viruses if your AV scanner 
goes into overdrive and its safe to add these programs (and their destinations) 
as AV over-rides.

I personally use DXKeeper as the central logging tool and use its "Export 
QSO's" function to "Export standard ADIF" back to the "wsjtx_log.adi" file 
(found in the location accessible by "File/Open Log Directory"). DXKeeper has 
great tools for managing duplicates. When all duplicates are removed 
periodically write them back to WSJT-X over-writing previous "wsjtx_log.adi" 
instances :-)

More info on how to do this and set up products can be found on each product's 
support forums :-)

73

Steve I
VK3VM / VK3SIR

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Bug report in mainwindow.cpp

2020-05-22 Thread Yukio JG1APX

Hello all

I have noticed minor things in mainwindow.cpp source code.  If they are
already known, sorry about this. 

v2.2.0 rc1 mainwindow.cpp :

1. FT4 background color of mode lable depends on previous mode. 
The background color difinition is missing in setup_status_bar
(bool vhf) at line 2275 :

if ("ISCAT" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #ff9933}");
  } else if ("JT9" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #ff6ec7}");
  } else if ("JT4" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #cc99ff}");
  } else if ("Echo" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #66}");
  } else if ("JT9+JT65" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #66}");
  } else if ("JT65" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #66ff66}");
  } else if ("QRA64" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #99ff33}");
  } else if ("MSK144" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #ff}");
  } else if ("FT8" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #6699ff}");
  } else if ("FreqCal" == m_mode) {
mode_label.setStyleSheet ("QLabel{background-color: #ff9933}");  }

2. m_send_RR73 from readSettings() at line 1203 :
  m_send_RR73=m_settings->value("RR73",37).toBool();
  '37' maybe typo.  True or false for Bool() instead.

73
Yukio JG1APX



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread DX Jami via wsjt-devel

 Jim,
I can do as you suggest or I can even interface WSJT-X with Log4OM and do it 
seamlessly.  I chose to do it as described to Murphy-proof things as much as 
possible and follow the KISS principle. 

Thanks for the comment Jim.  Have a great day.
    Danny    AH6FX/W4 - Virginia

On Friday, May 22, 2020, 4:39:35 PM EDT, Stephen VK3SIR 
 wrote:  

 Hi Michelle,

By far the best way to avoid duplicates in logs is to not set 
"Settings\Reporting\ Log automatically..." . If you come back with a RR73, auto 
log, and then a station comes back with a R-XX (what I term a "RR/73 Loop") 
then both communication and logging can lead to duplicates in logs.

Each logged entry should be manually approved (so do not check "Log 
automatically").

Some software loggers and bridges such as JTAlert (that I use and recommend 
heavily) also are not perfect. I use JTALert with DXLab's DXKeeper. No matter 
what I do sometimes (and erratically) a duplicate is logged to eQSL. These are 
issues for their support forums. Despite this forewarning  would strongly echo 
Jim's post and recommend JTAlert's use to you !

JTAlert can be found at  https://hamapps.com. DXLab can be found at 
https://dxlabsuite.com . None of these products are viruses if your AV scanner 
goes into overdrive and its safe to add these programs (and their destinations) 
as AV over-rides.

I personally use DXKeeper as the central logging tool and use its "Export 
QSO's" function to "Export standard ADIF" back to the "wsjtx.log" file (found 
in the location accessible by "File/Open Log Directory"). DXKeeper has great 
tools for managing duplicates. When all duplicates are removed periodically 
write them back to WSJT-X over-writing previous "wsjtx.log" instances :-)

More info on how to do this and set up products can be found on each product's 
support forums :-)

73

Steve I
VK3VM / VK3SIR

-Original Message-
From: Jim Preston  
Sent: Saturday, 23 May 2020 1:15 AM
To: DX Jami via wsjt-devel 
Subject: Re: [wsjt-devel] exporting from adi

Danny,

Why not just have JTAlert (if you use it) or WSJT-X log directly to Log4OM? 
Then you wouldn't have to go through the adif import routine.

73,

Jim N6VH

On 5/20/2020 6:45 PM, DX Jami via wsjt-devel wrote:
> Michelle,
> 
> My logging program is Log4OM ver2.  I routinely import my WSJT-x adi 
> files into Log4OM with no problems.  Most logging programs import only 
> current loggings.  Ensure you click something like “do not import 
> duplicates” in your logging program as you download and you should 
> have no problems.
> 
> Good luck.
> 
>   Danny
> 
>   AH6FX/W4 - Virginia
> 
> Sent from Mail  for 
> Windows 10
> 
> *From: *Michelle Sack via wsjt-devel
> 
> *Sent: *Wednesday, May 20, 2020 9:21 PM
> *To: *WSJT software development 
> 
> *Cc: *Michelle Sack 
> *Subject: *Re: [wsjt-devel] exporting from adi
> 
> I'm new to FT8 and WSJT software. Is a way to export from the log only 
> the recent contacts? This way I don't make duplicates in my logging 
> programs but still keep contacts in the WSJT log for notifications of 
> new (preventing duplicate contacts in FT8).
> 
> Thanks
> 
> Michelle N3YRZ
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread Stephen VK3SIR

Hi Michelle,

By far the best way to avoid duplicates in logs is to not set 
"Settings\Reporting\ Log automatically..." . If you come back with a RR73, auto 
log, and then a station comes back with a R-XX (what I term a "RR/73 Loop") 
then both communication and logging can lead to duplicates in logs.

Each logged entry should be manually approved (so do not check "Log 
automatically").

Some software loggers and bridges such as JTAlert (that I use and recommend 
heavily) also are not perfect. I use JTALert with DXLab's DXKeeper. No matter 
what I do sometimes (and erratically) a duplicate is logged to eQSL. These are 
issues for their support forums. Despite this forewarning  would strongly echo 
Jim's post and recommend JTAlert's use to you !

JTAlert can be found at  https://hamapps.com. DXLab can be found at 
https://dxlabsuite.com . None of these products are viruses if your AV scanner 
goes into overdrive and its safe to add these programs (and their destinations) 
as AV over-rides.

I personally use DXKeeper as the central logging tool and use its "Export 
QSO's" function to "Export standard ADIF" back to the "wsjtx.log" file (found 
in the location accessible by "File/Open Log Directory"). DXKeeper has great 
tools for managing duplicates. When all duplicates are removed periodically 
write them back to WSJT-X over-writing previous "wsjtx.log" instances :-)

More info on how to do this and set up products can be found on each product's 
support forums :-)

73

Steve I
VK3VM / VK3SIR

-Original Message-
From: Jim Preston  
Sent: Saturday, 23 May 2020 1:15 AM
To: DX Jami via wsjt-devel 
Subject: Re: [wsjt-devel] exporting from adi

Danny,

Why not just have JTAlert (if you use it) or WSJT-X log directly to Log4OM? 
Then you wouldn't have to go through the adif import routine.

73,

Jim N6VH

On 5/20/2020 6:45 PM, DX Jami via wsjt-devel wrote:
> Michelle,
> 
> My logging program is Log4OM ver2.  I routinely import my WSJT-x adi 
> files into Log4OM with no problems.  Most logging programs import only 
> current loggings.  Ensure you click something like “do not import 
> duplicates” in your logging program as you download and you should 
> have no problems.
> 
> Good luck.
> 
>   Danny
> 
>   AH6FX/W4 - Virginia
> 
> Sent from Mail  for 
> Windows 10
> 
> *From: *Michelle Sack via wsjt-devel
> 
> *Sent: *Wednesday, May 20, 2020 9:21 PM
> *To: *WSJT software development 
> 
> *Cc: *Michelle Sack 
> *Subject: *Re: [wsjt-devel] exporting from adi
> 
> I'm new to FT8 and WSJT software. Is a way to export from the log only 
> the recent contacts? This way I don't make duplicates in my logging 
> programs but still keep contacts in the WSJT log for notifications of 
> new (preventing duplicate contacts in FT8).
> 
> Thanks
> 
> Michelle N3YRZ
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread Paul Bramscher

Hi Claude,

Thanks, I'll take a look at that script.  Of course I locally keep and
backup all logs that I've ever generated.  If this tool automates these
kinds of merging issues, I'll certainly experiment with it.

73, KD0KZE / Paul

On 5/22/2020 1:06 PM, Claude Frantz wrote:
> On 5/22/20 7:22 PM, Paul Bramscher wrote:
> 
> Hi Paul & all,
> 
>> What I've done is maintain two local logs: WSJT-X's native log and XLog
>> for everything else.  fldigi will auto-ingest into XLog, and I can
>> easily enough create Phone and other entries manually in XLog.
> 
> Please note that fldigi is able to change entries in its log.
> Unfortunately such updates are not passed to Xlog.
> 
>> I periodically use TQSL to upload WSJT-X contacts to Logbook of the
>> World.  To make this more efficient, I examine my past activity date on
>> LoTW's interface and use my last upload date as the cut-off date for new
>> QSO's to upload.
> 
>> I also upload XLog logs there, so LoTW is the place where they all get
>> combined.  Then I occasionally export those and upload them into QRZ for
>> good measure.
> 
> adifmerg is an excellent program to merge ADIF log files.
> 
> Unfortunately, LoTW is not a good place to combine logs files because
> only a limited number of ADIF fields are maintained. Please remember
> that paper QSL exist too and many other things which are ignored by
> LoTW. Finally, only a locally maintained ADIF file can help to maintain
> all the information. And adifmerg can help you to do it. This is the way
> I'm going. With the optional addition of few user defined fields, such a
> locally stored ADIF file can be the base from which one an appropriate
> program can automatically generate detailed paper QSL cards. Of course,
> received QSL cards have to be mentioned in the appropriate records of
> the ADIF file.
> 
> Best wishes,
> Claude (DJ0OT)
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread Claude Frantz


On 5/22/20 7:22 PM, Paul Bramscher wrote:

Hi Paul & all,


What I've done is maintain two local logs: WSJT-X's native log and XLog
for everything else.  fldigi will auto-ingest into XLog, and I can
easily enough create Phone and other entries manually in XLog.


Please note that fldigi is able to change entries in its log. 
Unfortunately such updates are not passed to Xlog.



I periodically use TQSL to upload WSJT-X contacts to Logbook of the
World.  To make this more efficient, I examine my past activity date on
LoTW's interface and use my last upload date as the cut-off date for new
QSO's to upload.



I also upload XLog logs there, so LoTW is the place where they all get
combined.  Then I occasionally export those and upload them into QRZ for
good measure.


adifmerg is an excellent program to merge ADIF log files.

Unfortunately, LoTW is not a good place to combine logs files because 
only a limited number of ADIF fields are maintained. Please remember 
that paper QSL exist too and many other things which are ignored by 
LoTW. Finally, only a locally maintained ADIF file can help to maintain 
all the information. And adifmerg can help you to do it. This is the way 
I'm going. With the optional addition of few user defined fields, such a 
locally stored ADIF file can be the base from which one an appropriate 
program can automatically generate detailed paper QSL cards. Of course, 
received QSL cards have to be mentioned in the appropriate records of 
the ADIF file.


Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bug Report - 2.2rc1 - ISCAT Mode

2020-05-22 Thread Kevin McQuiggin

Thank you Joe, glad to help, if even with a little-used mode.

As others have said, we have a small group of ISCAT users here in the west, so 
we may have further info for you as time progresses.

We need to thanks James K7KQA for this as he is the driver out here for getting 
people to try out ISCAT.

Additional info is that the bug also exists in Windows.  As I stated I run 
WSJT-X on an iMac.

73 and thanks for all your (and the development group’s) great work.

Kevin VE7ZD/KN7Q

Sent from my iPhone

> On May 22, 2020, at 08:55, Joe Taylor  wrote:
> 
> Hi Kevin,
> 
>> On 5/22/2020 10:45 AM, Kevin McQuiggin VE7ZD/KN7Q wrote:
>> 
>> In ISCAT mode, if one double-clicks a message in the left hand RX signals 
>> pane this presents a dialog box “Double clicking is not supported in ISCAT 
>> mode”.  When this dialog box is dismissed, the app crashes.
> 
> Many tThanks for reporting this bug.  Who knows how many years it must have 
> been present?  It will be fixed in the coming "RC2" release of WSJT-X 2.2.0.
> 
>-- 73, Joe, K1JT

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread Paul Bramscher

What I've done is maintain two local logs: WSJT-X's native log and XLog
for everything else.  fldigi will auto-ingest into XLog, and I can
easily enough create Phone and other entries manually in XLog.

I periodically use TQSL to upload WSJT-X contacts to Logbook of the
World.  To make this more efficient, I examine my past activity date on
LoTW's interface and use my last upload date as the cut-off date for new
QSO's to upload.

I also upload XLog logs there, so LoTW is the place where they all get
combined.  Then I occasionally export those and upload them into QRZ for
good measure.

73, KD0KZE / Paul

On 5/20/2020 8:17 PM, Michelle Sack via wsjt-devel wrote:
> I'm new to FT8 and WSJT software. Is a way to export from the log only
> the recent contacts? This way I don't make duplicates in my logging
> programs but still keep contacts in the WSJT log for notifications of
> new (preventing duplicate contacts in FT8). 
> Thanks
> Michelle N3YRZ
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.2rc1 - usability comments

2020-05-22 Thread Alan Groups


Hi, just tried this out on some 10m Es using FT8:

I find the two stage display of decodes a little disconcerting; the 
double flash of the decode button doesn't help - adds more visual 
clutter?  Could the user maybe have a choice to temporarily cache the 
early decodes and then show them all at once along with the later decodes?


"The Status bar now displays the number of decodes found in the most 
recent Rx sequence" - this needs a box to say what it is on mouse hover, 
or maybe simpler to say "Rx decodes: xx" rather than just "xx".


Compared to 2.1.2 there are definitely more decodes in the band activity 
box.


Not a specific 2.2 RC1 comment but generally would be nice if "Tune" 
could use a CAT code to reduce rig power output if the user wanted - 
useful for auto-ATU's.  Even better if that could happen automatically 
on band change should the user want it!


Alan G0TLK


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] [WSJTX] Bug Report - 2.2rc1 - ISCAT Mode

2020-05-22 Thread iain macdonnell - N6ML

On Fri, May 22, 2020 at 8:55 AM Joe  wrote:
>
> Hi Kevin,
>
> On 5/22/2020 10:45 AM, Kevin McQuiggin VE7ZD/KN7Q wrote:
>
> > In ISCAT mode, if one double-clicks a message in the left hand RX signals 
> > pane this presents a dialog box “Double clicking is not supported in ISCAT 
> > mode”.  When this dialog box is dismissed, the app crashes.
>
> Many tThanks for reporting this bug.  Who knows how many years it must
> have been present?  It will be fixed in the coming "RC2" release of
> WSJT-X 2.2.0.

Funny; I just came here to report the same thing! :) There is a group
out this way experimenting with ISCAT.

Is there a reason (other than developer time) that double-click isn't
implemented? It'd be convenience to populate the "DX Call" and "DX
Grid" fields from a clean decode, at least.

Another minor issue: On launching 2.2.0-rc1 (haven't checked older
versions), having operated ISCAT submode B on last use, it comes up
with "ISCAT B" in the status bar at the bottom, but the selector
thingie (spinbox??) shows "Submode A". I'm not sure which submode it's
actually using at that point - I always "spin the spinbox"(?) to make
sure.

73,

~iain / N6ML

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bug Report - 2.2rc1 - ISCAT Mode

2020-05-22 Thread Joe Taylor


Hi Kevin,

On 5/22/2020 10:45 AM, Kevin McQuiggin VE7ZD/KN7Q wrote:


In ISCAT mode, if one double-clicks a message in the left hand RX signals pane 
this presents a dialog box “Double clicking is not supported in ISCAT mode”.  
When this dialog box is dismissed, the app crashes.


Many tThanks for reporting this bug.  Who knows how many years it must 
have been present?  It will be fixed in the coming "RC2" release of 
WSJT-X 2.2.0.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Bug Report - 2.2rc1 - ISCAT Mode

2020-05-22 Thread Kevin McQuiggin

Hi All:

In ISCAT mode, if one double-clicks a message in the left hand RX signals pane 
this presents a dialog box “Double clicking is not supported in ISCAT mode”.  
When this dialog box is dismissed, the app crashes.

I am running rc1 on MacOS version 10.14.6 Mojave.

If you need further info then please email me.

73,

Kevin VE7ZD/KN7Q




signature.asc
Description: Message signed with OpenPGP
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

2020-05-22 Thread Jim Preston


Danny,

Why not just have JTAlert (if you use it) or WSJT-X log directly to 
Log4OM? Then you wouldn't have to go through the adif import routine.


73,

Jim N6VH

On 5/20/2020 6:45 PM, DX Jami via wsjt-devel wrote:

Michelle,

My logging program is Log4OM ver2.  I routinely import my WSJT-x adi 
files into Log4OM with no problems.  Most logging programs import only 
current loggings.  Ensure you click something like “do not import 
duplicates” in your logging program as you download and you should have 
no problems.


Good luck.

  Danny

  AH6FX/W4 - Virginia

Sent from Mail  for 
Windows 10


*From: *Michelle Sack via wsjt-devel 


*Sent: *Wednesday, May 20, 2020 9:21 PM
*To: *WSJT software development 
*Cc: *Michelle Sack 
*Subject: *Re: [wsjt-devel] exporting from adi

I'm new to FT8 and WSJT software. Is a way to export from the log only 
the recent contacts? This way I don't make duplicates in my logging 
programs but still keep contacts in the WSJT log for notifications of 
new (preventing duplicate contacts in FT8).


Thanks

Michelle N3YRZ



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

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

2020-05-22 Thread Neil Zampella


Well ... the 73 is what triggers the WSJT-X log panel.    As far as the
multiple RRR/RR73s, the RRR users send DO expect a 73 from you (at least
the system does), the RR73 users have no clue.

Neil, KN3ILZ

On 5/21/2020 6:17 PM, Al Pawlowski wrote:

Actually, just discovered that WSKJTx already almost does this.
Putting a blank line in the tx5/custom message window during a QSO
will cause a tx disable after tx4 - whether you sent the first CQ or
not. However, the auto-log window popup does not work unless a
tx5/custom non-blank message is sent.

BTW, in testing this on 4 QSO’s, all 4 of my QSO partners sent
multiple RRR/RR73’s (after not getting a 73 from me).

Al Pawlowski, K6AVP
Los Osos, CA USA




Begin forwarded message:

*From: *Al Pawlowski mailto:k6...@almont.com>>
*Subject: **Re: Clicking on RR73 produced wrong TX response msg*
*Date: *May 21, 2020 at 09:37:11 PDT
*To: *wsjt-devel@lists.sourceforge.net


A nice new feature for WSJTx might be to not reset the
custom (tx5) message (to CS 73) for a QSO and instead skip, or end
with,  tx5 depending on the message content, i.e. a blank (or ***
say) in the window would mean skip - it might even make sense to make
the skip message the default.


Al Pawlowski, K6AVP
Los Osos, CA USA




On May 20, 2020, at 16:52, wsjt-devel-requ...@lists.sourceforge.net
 wrote:

Date: Wed, 20 May 2020 16:51:57 -0700
From: Paul Kube mailto:paul.k...@gmail.com>>
To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Clicking on RR73 produced wrong TX response
msg

On Wed, May 20, 2020 at 2:05 PM Gary McDuffie mailto:mcduf...@ag0n.net>> wrote:



If you call letting him know that you got his acknowledgement of your
report a courtesy, I guess so.  I call it a necessity in order to
allow him
to move on.  If I don?t send the 73, it means I didn?t get his
RR73.  If he
doesn?t finish, he isn?t in the log.



If you didn't get his RR73 (Tx4), certainly the thing to do is to resend
your report (Tx3), no?

On the other hand, if you did get his RR73, you can consider the QSO
completed, and respond in whatever way you want. At least, that's
the view
I've come to after using the FT* modes since they were invented. Was it
"really" a QSO? I'll let LoTW or the contest logcheck software sort
it out.

A special case is when I see a station I've worked sending RR73
again. That
shows they're probably expecting a 73 from me and didn't get it. So
in that
case I'll send 73 (Tx5, which is totally customizable, there's even a TX
Macros page in Settings that lets you create a whole library of
them). But
that almost never happens anymore.







--
This email has been checked for viruses by AVG.
https://www.avg.com
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

[wsjt-devel] Bug report in mainwindow.cpp

Re: [wsjt-devel] exporting from adi

Re: [wsjt-devel] exporting from adi

Re: [wsjt-devel] exporting from adi

Re: [wsjt-devel] exporting from adi

Re: [wsjt-devel] Bug Report - 2.2rc1 - ISCAT Mode

Re: [wsjt-devel] exporting from adi

Re: [wsjt-devel] 2.2rc1 - usability comments

Re: [wsjt-devel] [WSJTX] Bug Report - 2.2rc1 - ISCAT Mode

Re: [wsjt-devel] Bug Report - 2.2rc1 - ISCAT Mode

[wsjt-devel] Bug Report - 2.2rc1 - ISCAT Mode

Re: [wsjt-devel] exporting from adi

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

14 matches

Site Navigation

Mail list logo

Footer information