Everyone paying attention should already know what's contained in this
message -- but it's clear that some do not.
The current General Availability (GA) release of WSJT-X is v1.8.0. That
program version does not include FT8 DXpedition Mode.
We have made beta-level "release candidates" availa
And about the expedition using DXp without the authorization of the
development team (and who did not read the readme file either):
I find, for one, that they are doing a very good job. They found how to
publicize their expedition (freq and time),
and, with the number of bugs in the app, they
We are all experimenters. Give us a tool that is new and we will use it
and shake it until it exhauts.
You know we would use the DXp side of WSJT-X as soon as you released
it. Because it's new, because it's shining, because it's what we
expected, because we don't know what to expect but we ar
The problem is Serge, that they picked frequencies that are normally in
use by other modes, thus causing more problems then Fox & Hounds solves,
as they did not consider the consequences of those actions.
Neil, KN3ILZ
On 3/29/2018 3:45 PM, F6BHK wrote:
And about the expedition using DXp witho
WSJT software development
Subject: [wsjt-devel] Premature use of FT8 DXpedition Mode
Everyone paying attention should already know what's contained in this message
-- but it's clear that some do not.
The current General Availability (GA) release of WSJT-X is v1.8.0. That
program v
on frequency selection. You will note from my blog I
> have elected to use alternate frequencies that differ from your proposals. I
> am happy to discuss my choices and justifications down the track.
>
>
>
>
> -Original Message-
> From: Joe Taylor [mailto:
Hi !
Do we get 1.9.0-rc4 for the next test, or should latest r to be
compiled from source and used (if possible)?
Question is because lot of rc3 bugs are known and perhaps we should step
forward to see the effect of fixes and find new (lately added!!??) bugs.
--
Saku
OH1KH
Joe Taylor k
On 30/03/2018 08:04, Saku wrote:
Hi !
Do we get 1.9.0-rc4 for the next test, or should latest r to be
compiled from source and used (if possible)?
Question is because lot of rc3 bugs are known and perhaps we should
step forward to see the effect of fixes and find new (lately
added!!??)
On 30/03/2018 12:34, Bill Somerville wrote:
The only one that is even closely related is a fox of a defect that
stopped the "Tune" button working for Hounds when the "DX Call" entry
is blank, the work-around is obvious.
I have no idea how that sentence came about, I meant to type:
The only on
? What is the plan?
Dave / NX6D
From: Neil Zampella
Sent: Thursday, March 29, 2018 1:45:47 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Premature use of FT8 DXpedition Mode
The problem is Serge, that they picked frequencies that are
I think all we need to do is discourage use by the casual user.
I proposed this idea earlier but never heard any feedback.
#1 Add a Dxpedition flag to the frequency list (defaults to off).#2 If the
Dxpedition flag is false then the Fox/Hound boxes are disabled (or even
hidden). If you aren't run
Title: Re: [wsjt-devel] Premature use of FT8 DXpedition Mode
Mike,
a perfect idea! Just got a 'support call' - he can not TX, he wants to call CQ(???).
The guy activated 'Hound', because he wanted to be ready, if any DXPedition
shows up!
The Fox & Hound boxes s
12 matches
Mail list logo
