Can you show a screen snapshot?
Yours looks different than this?
de Mike W9MDB
On Wednesday, February 28, 2018, 6:34:58 PM CST, Jim Record
wrote:
Courier font, Windows 10 Pro, latest release - still poor lineup. Also CQ not
padded.
Jim
On Wed, Feb 28, 2018 at 10:11 AM Black Michae
Courier font, Windows 10 Pro, latest release - still poor lineup. Also CQ
not padded.
Jim
On Wed, Feb 28, 2018 at 10:11 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> It also sounds like you've chosen a non-proportional font.
> With a proportional font they line up
On 1/03/2018 7:54 AM, David Fisher wrote:
That would be VERY useful. I hope you can get it into the code. Does
it involve changes to JTAlertX?
Dave / NX6D
Dave,
Probably not. JTAlert already sends the required UDP instruction to
WSJT-X regardless of the decode type. WSJT-X currently i
: Re: [wsjt-devel] Space pad for readability
I've got a better solution in the works.
I'm testing a patch that allows you to click non-CQ messages in JTAlert and it
will set up the call without enabling Tx. You can rapidly click on most (if
not all) non-CQ messages to queue them up
It also sounds like you've chosen a non-proportional font.With a proportional
font they line up OK.
Try Courier for example and see if that lines them up for you.
de Mike W9MDB
--
Check out the vibrant tech community on
I've got a better solution in the works.
I'm testing a patch that allows you to click non-CQ messages in JTAlert and it
will set up the call without enabling Tx. You can rapidly click on most (if
not all) non-CQ messages to queue them up in your Rx window. No more hunting in
the Band window nee
How about space padding the first two fields of the Message part of the
Band Activity window so that each is at least seven characters long? The
result would be that these two fields would line up for most messages. This
would make it easier to visually scan the Band Activity window for call
signs,
