That was the way it always was in EME before Q65...everybody was OOO. I
still wish there were some option for that and for an initial CALL3.TXT
lookup so I could see who was calling me on what frequency. I have been
guessing like mad typing in various callsigns into the DX STATION
callsign box
Lance, W7GJ wrote:
...Maybe if there were an option to keep the signal report the
same even if there are a number of intervening contacts or transmissions to
other stations, I guess that is what I am trying to do by hand and failing
miserably at... Do you understand my dilemma?
MNI
On 25/10/2021 15:58, Martin Davies G0HDB via wsjt-devel wrote:
On 25 Oct 2021 at 12:44, Bill Somerville via wsjt-devel wrote:
Hi Saku,
it's not quite that simple. The width of a window is the sum of the
widths demanded by the widgets and layouts contained within it. There is
a regression in
On 25 Oct 2021 at 12:44, Bill Somerville via wsjt-devel wrote:
> Hi Saku,
>
> it's not quite that simple. The width of a window is the sum of the
> widths demanded by the widgets and layouts contained within it. There is
> a regression in 2.5.1 which means the main window width is larger than
I was just about to report this too - I use WSJTx in Windows. Glad the
change/bug has been caught and will be fixed.
FWIW, I have WSJTx opening on an “expanded desktop” (21”) monitor attached to
my (17”) laptop. WSJTx does remember the previous left side positioning, but
not the last set
On 25/10/2021 12:26, Saku via wsjt-devel wrote:
Just compiled version 2.5.1 (from sourceforge).
When I first started that one the main window was about 6cm wider than
old one in my display.
I could shrink it to back reasonable width (those 6cms), but when I
closed it and started again it's
Just compiled version 2.5.1 (from sourceforge).
When I first started that one the main window was about 6cm wider than
old one in my display.
I could shrink it to back reasonable width (those 6cms), but when I
closed it and started again it's again back to that huge width.
After that I
