Folks,
I agree wholeheartedly that the facility is there already for respected
contributors to feed back comments that are handled well by the development
team within the JT software development ranks.
The issue will be the “wombats” (as we term them here in Australia) that
suddenly see more s
Hello to the Dev team,
with the impeding release of version 2.0 'gold' in December I have
started to put threads into some of the more active local forums in VK to
alert those who may not know that a new MAJOR update of WSJT-X is coming
and that FT8 and MSK modes will be changing. I have requeste
Brian, it appears you don't understand email reflectors vs email lists.
There has never been an expectation that anyone read all the emails that
come via the reflector.
There is a search function right on the Dev List page that anyone who is
reporting bugs should check first to see if what the
With all due respect, I suppose the point of having this list is for RC users
to report possible bugs to the developers. You are hardly encouraging the
average user to report anything.
73 de Tom OH6VDA / JW6VDA
> 23. nov. 2018 kl. 20:37 skrev Brian Moran :
>
> --1e7560057b594819
WSJT-X represents current state of the art for weak signals in Amateur
Radio communications, but using 'email as a bug database' to keep track of
issues decidedly does NOT represent the state of the art in anything.
Asking everyone to read all of the emails to see if their issue is
represented befo
Hi Richard
Well the LOTW problem , can’t decode 75 bit message are both in the
Release/Quick Start guide - but that is beside the point
The new page would address it - the only source of the RC downloads is via the
princeton site (mind you I think if it were hosted outside the US then the
dev
How about a web page only for bugs?
Could be put in the Help menu "Known Bugs/Issues" and doesn't require a new
release to keep current. A section for each release would be appropriate
showing "Fixed" status too.
Users would eventually learn to check that first avoiding most of the repeat
q
Tom,
Regarding your comments about the release notes, if fact almost all of
the issues that I addressed as examples are NOT covered in the latest
released notes.
I do like your idea of having to go to another page to read the list of
known issues (and then possibly having to check a box?) befor
Do you think that would help 90% of the posters - sorry I don’t think so.
The 77 bit signal and LOTW errors are very clearly mentioned in the release
notes - which everyone is advised to read but don't
Those looking at the mailing lists - there is an archive/search option - even
just reading wh
Bill, et al,
Wouldn't it be a good idea to post a list of known WSJT-X issues on a
regular basis? We all see SO MANY repeat posts complaining about problems
being experienced with release candidates. Hopefully, posting such a list
would greatly reduce repeat problem complaints.
Some known issues c
10 matches
Mail list logo
