Re: [wsjt-devel] WSJT-X 1.4 changed behaviour, not responding to winapi positioning commands

2014-04-06 Thread Laurie VK3AMA
Hi Bill, Sounds like it is the new Qt code. I have no experience with Qt but it has been the root of some of the issues I have had to overcome for JTAlert. I am getting the window handle by enumerating the running wsjtx processes. I know I am using the correct handle as the window minimize/r

Re: [wsjt-devel] WSJT-X 1.4 changed behaviour, not responding to winapi positioning commands

2014-04-06 Thread Bill Somerville
On 07/04/2014 01:19, Laurie VK3AMA wrote: Hi Laurie, I have been extending JTAlert to support the new 1.4 multi-instance functionality. JTAlert docking is now broken with 1.4. Standard api commands, ShowWindow(), MoveWindow() and SetWindowPos() sent by JTAlert to the wsjtx window are being igno

[wsjt-devel] WSJT-X 1.4 changed behaviour, not responding to winapi positioning commands

2014-04-06 Thread Laurie VK3AMA
I have been extending JTAlert to support the new 1.4 multi-instance functionality. JTAlert docking is now broken with 1.4. Standard api commands, ShowWindow(), MoveWindow() and SetWindowPos() sent by JTAlert to the wsjtx window are being ignored. I have been able to workaround the loss of Show

Re: [wsjt-devel] WSJT-X Latest revision - CW ID broken.

2014-04-06 Thread Bill Somerville
On 04/04/2014 18:40, Bill Somerville wrote: > Hi All, Hi again, > > the current WSJT-X has a defect in the CW ID generation that means it is > truncated or garbled most of the time. This is as a result of some > changes I made recently. So if you locale requires a CW ID I would avoid > using the cu