w4kek/WSJT-X
1
0
Fork 0
mirror of https://github.com/saitohirga/WSJT-X.git synced 2025-07-30 12:42:27 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update issue-log.

Browse Source 
git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-1.4@4467 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This commit is contained in:
Joe Taylor 2014-10-03 16:41:57 +00:00
parent 842a4c9437
commit bfa64afe06
1 changed files with 17 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
issue-log.txt
View File

@ -196,6 +196,8 @@ Waterfall - Jean f8rz - Requesting different labelling
Proposed for v1.5.
Implemented by Joe in r4464. (Others please test!)
Decoding - Jean f8rz - Abandoned Tx should not disable decoding for a period
This is an outstanding issue in at least v1.3 also.
@ -208,6 +210,10 @@ Decoding - Jean f8rz - Abandoned Tx should not disable decoding for a period
buffering may be an option. Question: is the audio buffer
needed after the last symspec call?
K1JT: I agree that this has been a desirable change. Perhaps
can zero only a small part of the buffer -- samples taken
while Tx was on?
Decoded text - Albert kc8kjf - Report or grid last character truncated
This occurs with larger fonts sizes on long decoded text lines
@ -222,6 +228,11 @@ Decoded text - Albert kc8kjf - Report or grid last character truncated
Proposed for v1.5.
K1JT: on the system I tested, it was OK after making the main
window a bit wider. It has something to do with having
selected "Show DXCC entity and worked before status" when the
main window was not (then) large enough?
HRD FTDX3000 - Jean-Michel f6eao/p - Not working
This as yet untested rig with WSJT-X + HRD clearly needs some
@ -231,10 +242,10 @@ HRD FTDX3000 - Jean-Michel f6eao/p - Not working
Multi-instance support - Bill g4wjs - Lock mechanism needed to avoid duplicates
There is no check that multiple instances are being run
with the same rig-name. Some mechanism to control this
is desirable. A simple mechanism that isn't prone to
false positives (i.e. not relying on lock files being
deleted on exit) needs to be developed.
There is no check that multiple instances are being run with
the same rig-name. Some mechanism to control this is
desirable. A simple mechanism that isn't prone to false
positives (i.e. not relying on lock files being deleted on
exit) needs to be developed.
Implemented in v1.5. - Closed.
Implemented in v1.5. - Closed.