Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Martin Davies G0HDB
On 25 May 2021 at 11:54, Harry E. Hoffman wrote: > I have also noticed this in both the 4 RC releases and the General > release of 2.4.0. I have many different configurations and it appears > that the problem exists only in the configurations where I did a RESET > in the frequency list. The pul

Re: [wsjt-devel] ?= =?utf-8?q? V2.4.0 TX report setting

2021-05-25 Thread Bill Somerville
Hi Svein, the sent report value is not "frozen" until the first time it is transmitted. 73 Bill G4WJS. On 25/05/2021 19:26, SVEIN BERGSTØL wrote: Hi Bill, Thanks for the explanation. I never change a report after a connection is established, but sometimes I call a station for a long time b

Re: [wsjt-devel] ?==?utf-8?q? ?==?utf-8?q? V2.4.0 TX report setting

2021-05-25 Thread SVEIN BERGSTØL
Hi Bill, Thanks for the explanation. I never change a report after a connection is established, but sometimes I call a station for a long time before I get an answer, and if propagation change, I like to update the report. I know I can use the spin box.  It makes sense about message averaging

Re: [wsjt-devel] V2.4.0 TX report setting

2021-05-25 Thread Bill Somerville
On 25/05/2021 18:05, SVEIN BERGSTØL wrote: Hi, I have installed V2.4.0 successfully, and it seems to work fine. I have noticed a change in the way the TX report is set when I double-click a spot: The first time a call is clicked, the report is set correctly according to the spot signal strength

[wsjt-devel] V2.4.0 TX report setting

2021-05-25 Thread SVEIN BERGSTØL
Hi, I have installed V2.4.0 successfully, and it seems to work fine. I have noticed a change in the way the TX report is set when I double-click a spot: The first time a call is clicked, the report is set correctly according to the spot signal strength. If I want to update the report if the sign

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Harry E. Hoffman
I have also noticed this in both the 4 RC releases and the General release of 2.4.0. I have many different configurations and it appears that the problem exists only in the configurations where I did a RESET in the frequency list. The pull down window gets wide enough to show all the characters

Re: [wsjt-devel] Feature Request: Highlight DX Call

2021-05-25 Thread Jon Anhold
Sorry for multiple emails, but I meant to add: this would highlight any decodes from that callsign, not just CQs. Thanks & 73 On Tue, May 25, 2021 at 11:42 AM Jon Anhold wrote: > I think it would be useful if there was a way to configure highlighting of > decodes matching the callsign currentl

[wsjt-devel] Feature Request: Highlight DX Call

2021-05-25 Thread Jon Anhold
I think it would be useful if there was a way to configure highlighting of decodes matching the callsign currently in the DX Call box. For example, you see a spot for KM8V on 18.100 so you tune to that frequency. You pop KM8V into the DX Call box, and in the Band Activity window, if you are decodi

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Reino Talarmo
>I can reproduce that here when I change the Font size to a larger value (File, Settings, Font). Changing it to a lower value reduces or eliminates the problem. I am on GA release v2.4.0 c19d62. I no longer have RC4 installed. Still a further pierce of information in both PCs I have font MS Shell

Re: [wsjt-devel] wsjt-devel Digest, Vol 87, Issue 37

2021-05-25 Thread Al Pawlowski
I forgot about font sizing. I run in “10”. Definitely plays a part in how many characters are displayed in the band dropdown. Even though the overall program window enlarges, it does not do so enough to maintain character width. Increasing display font to “18", for instance, my menu goes from 6

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Sam W2JDB via wsjt-devel
Hi, Running Win/10 with 2.4GA. No problem at all.  Make sure you reset all the frequencies. Click on the frequency tab on the settings page, bring up the popup menu and select reset. 73, Sam W2JDB -Original Message- From: Al Pawlowski To: WSJT software development Sent: Tue, May 25,

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Dennis Younker NE6I
I can reproduce that here when I change the Font size to a larger value (File, Settings, Font). Changing it to a lower value reduces or eliminates the problem. I am on GA release v2.4.0 c19d62. I no longer have RC4 installed. --Dennis NE6I -Original Message- From: Martin Davies G0HDB Se

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Al Pawlowski
I too skipped the rc’s for this latest version, am running Win10 latest and just installed the 64bit GA release. My drop down band is normal, shows the same width as the 2.3 GA release. At first glance, all else appears to be running normally too. I am seeing some additional VHF/UHF bands, whic

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Reino Talarmo
>I see it also in v2.4.0-rc4, just checked not used it actively as all my use >been only on 20n band, hi! 73, Reino OH3mA Additional information for this feature. I am using Windows 10 and having the narrow drop down list (extends about four capital letters less than in the second one) Editio

Re: [wsjt-devel] WSJT-X 2.4.0 User Guide: Where to send translations? Proposals for corrections/updates.

2021-05-25 Thread Joe Taylor
Hi Frode, Thanks for your proposed corrections to the WSJT-X User Guide, and please accept my apology for failure to publish your Norwegian translation of the v2.3 Guide. With concurrent work on Q65, WSJT-X 2.4, Hamlib 4.2, and MAP65 3.0, some required tasks have been on hold for too long.

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Reino Talarmo
I see it also in v2.4.0-rc4, just checked not used it actively as all my use been only on 20n band, hi! 73, Reino OH3mA 50.3...(6m) Has anyone else observed this 'feature' in v2.4.0? ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https:

Re: [wsjt-devel] v2.4.0 GA (possible bug?)

2021-05-25 Thread Martin Davies G0HDB
I never got round to installing and trying any of the -RC versions of v2.4.0 but last night (Mon 24th) I downloaded and installed the 64-bit GA release, v2.4.0 (c19d62). My PC, a Dell 3070, is running Win10 (fully up to date); the PC has a 3.0GHz i7-9700 8-core CPU with 16G RAM and a 256G SS