Hi Dave, Jim, and all,
On 7/4/2018 8:56 PM, Jim Brown wrote:
On 7/4/2018 4:40 PM, David Fisher wrote:
Later when I uploaded to ClugLog, I was reminded that I logged the
wrong callsign. Easily fixed in ClubLog, but for LOTW, all I could do
was log the contacts again as KH1/KH7X.
I also simpl
The FT8 DXpedition Mode User Guide is now available on the WSJT web site
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
in English, German, Polish, Norwegian, Finnish, Japanese, and Portuguese.
Many thanks to OE1EQW, SP9TTG, LA6VQ, OH1KH, JA7UDE, and CT1EKD for the
translations!
-
On 7/5/2018 5:26 AM, Joe Taylor wrote:
There should be no need to edit the prefix in DXKeeper. When attempting
to work a DXpedition you know their callsign perfectly well, in advance.
Yes, but -- when you click on their call when they have called someone
else, you get KH7W, not KH1/KH7W, WSJT
Jim --
On 7/5/2018 12:49 PM, Jim Brown wrote:
On 7/5/2018 5:26 AM, Joe Taylor wrote:
There should be no need to edit the prefix in DXKeeper. When
attempting to work a DXpedition you know their callsign perfectly
well, in advance.
Yes, but -- when you click on their call when they have calle
So let's change the double-click on the Band Activity and tell them that rather
than processing it."You must enter the DXpedition call yourself in the DX Call
box".
de Mike W9MDB
On Thursday, July 5, 2018, 11:56:20 AM CDT, Joe Taylor
wrote:
Jim --
On 7/5/2018 12:49 PM, Jim Brown
That approach seemed to work for me.
73
Mark Spencer
VE7AFZ
netsyn...@gmail.com
> On Jul 5, 2018, at 9:59 AM, Black Michael via wsjt-devel
> wrote:
>
> So let's change the double-click on the Band Activity and tell them that
> rather than processing it.
> "You must enter the DXpedition
Joe
I think there has been confusion in the ranks from two different
instructions to hounds.
Baker's website says to click a decode, and your instructions clearly
state to put the full expedition call into the DX box.
I followed your instructions.
Charlie
Hi Charlie and all,
On 7/5/2018 1:51 PM, char...@sucklingfamily.free-online.co.uk wrote:
Joe
I think there has been confusion in the ranks from two different
instructions to hounds.
Baker's website says to click a decode, and your instructions clearly
state to put the full expedition call int
Simple patch to solve this problem...
@@ -4031,6 +4031,10 @@ void
MainWindow::doubleClickOnCall2(Qt::KeyboardModifiers modifiers)
void MainWindow::doubleClickOnCall(Qt::KeyboardModifiers modifiers)
{
+ if (m_config.bHound()) {
+ MessageBox::information_message(this,"You must enter the DXp
Joe,
I am waiting your response to my previous message to recalculate additional
gain for myself.
To make sure my intention, I described the inquiry as follow.
One FT8 frame has 7x7x3 =147 bits synch words and I understand current DX
Pedition mode locates them in each FDM slot. Thus, we can sh
Sure, I knew the callsign, but people make mistakes.
When I start the program in Hound mode, it reminds me (unnecessarily) to switch
to “fake it” mode. In my case the nag box is an annoyance since I run a Flex
6600. Why nag users about this? Because people make mistakes, and the program
is
11 matches
Mail list logo
