On 16/09/2017 05:36, Richard Lamont wrote:
On 15/09/17 21:56, Bill Somerville wrote:
On 15/09/2017 21:08, DG2YCB, Uwe wrote>> Why is there now such a big space
between the Message text and the
DXCC entity? It was better in the old version 1.7.0.
before WSJT-X v1.8.0 RC2 the space was truncated but that can no longer
be done as important information goes in that gap.
Could it be reduced if AP is turned off?
Hi Richard,
not really. The reason is that WSJT-X does not save decode information
anywhere other than in the text of the decodes windows, this makes it
impossible to know what settings were in effect when a decode was made.
This also makes it near impossible to strip off any added information as
there is no delimiter. This is a design deficiency we are aware of and
wish to resolve but it is so fundamental in the application that it will
take some time to manoeuvre the implementation to a place where we can.
There is no wish to do a wholesale rewrite so this will take some time
to get to incrementally.
One possible interim measure might be to add a delimiter character that
allows the application to distinguish between message text, and quality
information like AP indicators, from the added worked before and DXCC
entity name information. That would allow the multiple spaces to be
reduced to one, or to a fixed column, so that only lines where the
message was long or quality information was present would require the
worked before and DXCC entity name information to be pushed to the right.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
