Bug with Change for poll 420 #463
Conversation
When logging contacts it is not working as intended here. I noticed that when I log a station in WSJT-X the Status wipes the callsign before the logged message goes through so the information is not there to save. I'm not sure if this is the best way to address but it seems to work. Not sure if it needs to be fixed a different way.
|
To make it make sense, I added WWFF, SOTA, and SIG. As for changeCallsignManually, I'm not sure about it, so I left it out. WSJTX is now logged in a different way, and the QSY Wipe can be disabled. So I think it's not necessary. See modified commit a4e9e71 (the typo WJSTX was corrected in another commit) |
|
Sounds good to me, glad you added the other fields. I know for me after I
disabled the QSY Wipe I also had to disable a setting in
WSJTX-Improved 'Clear DX Call after QSO'. But when I did that it works as
I would expect now.
[image: image.png]
…On Wed, Sep 25, 2024 at 10:48 AM Ladislav ***@***.***> wrote:
To make it make sense, I added WWFF, SOTA, and SIG. As for
changeCallsignManually, I'm not sure about it, so I left it out. WSJTX is
now logged in a different way, and the QSY Wipe can be disabled. So I think
it's not necessary. See modified commit a4e9e71
<a4e9e71>
(the typo WJSTX was corrected in another commit)
—
Reply to this email directly, view it on GitHub
<#463 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUEEMXRW2CJNAAROTX3H4U3ZYLLOFAVCNFSM6AAAAABOHC4PZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGQ3DQNZRGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Please, could you test the latest pre-release branch, testing_0.39, to check if it's still necessary to keep QSY Wipe turned off? |
|
If I enable QSY Wiping it is doing like before. If I double click on a station in WSJTX it loads the info in QLog but as soon as it transmits all the info wipes away. Here's quick video showing: https://youtu.be/H-mI4519SiA?si=0c8SgjvzXwcZ-wHk |
|
Could you please also send me a screenshot of your rig settings for this case? |
|
Here you go.
[image: image.png]
…On Thu, Sep 26, 2024 at 7:48 AM Ladislav ***@***.***> wrote:
Could you please also send me a screenshot of your rig settings for this
case?
—
Reply to this email directly, view it on GitHub
<#463 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUEEMXTBR3M4U63RHH4UI23ZYP7BDAVCNFSM6AAAAABOHC4PZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWHA2TQOJWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
|
|
The testing_0.39 branch has been updated to prevent the QSY Wipe in this case. I believe an elegant workaround was used - running the QSO Timer. |
|
That is a really good idea. I will test it out in a little while.
… On Sep 27, 2024, at 3:09 AM, Ladislav ***@***.***> wrote:
The testing_0.39 branch has been updated to prevent the QSY Wipe in this case. I believe an elegant workaround was used - running the QSO Timer.
—
Reply to this email directly, view it on GitHub <#463 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXU5WPWS22L3ABGJ2LTZYUHDDAVCNFSM6AAAAABOHC4PZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZYGY4DQNJQGI>.
You are receiving this because you authored the thread.
|
|
It is a part of the v0.39 |
When logging contacts it is not working as intended here. I noticed that when I log a station in WSJT-X the Status wipes the callsign before the logged message goes through so the information is not there to save. I'm not sure if this is the best way to address but it seems to work. Not sure if it needs to be fixed a different way.