Re: [wsjt-devel] Anything in the UDP code that may break DDE?

[Bill S. <g4...@cl...>]

On 28/05/2016 20:17, Laurie VK3AMA wrote:
> After a PC reboot the problems persisted.
> They disabled the UDP settings with WSJT-X, rebooted, yet the broken DDE
> remained.
>
> They advised the only way to restore DDE functionality was to perform a
> System Restore.
>
> I suggested that a System Restore should not have been needed and that
> all they needed to do was turn off the WSJT-X UDP. They were adamant
> that turning off UDP didn't correct the problem (even after a PC
> restart) and that they had tried 3 different times and each time, the
> only way to restore DDE Functions was a System Restore.
>
> Is there anything in the UDP code that is changing Comms settings at the
> OS level when UDP is first enabled that are not getting reversed when
> UDP is turned off? Perhaps it is something within the QT library?

Hi Laurie,


there may be some confusion about "turning off" UDP messages in WSJT-X. 
The check boxes only determine the behaviour of WSJT-X with respect to 
incoming UDP traffic. To start WSJT-X without it sending outgoing UDP 
messages the port number must be set to zero or the server name/address 
must be set to an empty string.


The only change to UDP messaging in WSJT-X recently is at r6691 with the 
status message being extended with new fields. From your other messages 
it looks like the OM was using an older generation of the development 
branch.


I doubt that anything WSJT-X does could impact DDE communications 
between other applications but anything is possible even if remote. 
Given the recent issues with DDE in the MS Insider Preview Fast Ring 
Windows 10 pre-releases; I have to wonder if the OM was using a 
pre-release Windows 10 Beta?


If the OM can get WSJT-X v1.7.0-devel to "break DDE" again, I would 
interested to know if simply setting the UDP service port to zero in 
WSJT-X "Settings->Reporting" clears the issue.


73
Bill
G4WJS.