Re: [TCLCORE] Tcl 8.6.9 Release Candidate

[Francois V. <fvo...@fr...>]

Le 14/10/2018 à 13:58, Harald Oehlmann a écrit :
> Am 12.10.2018 um 22:49 schrieb Francois Vogel:
>> On what version of Windows did you test Tk? I think you said
>> previously you are running Win 10? Remember:
>>
>>      https://core.tcl.tk/tk/info/69b48f427e94899a
> I double-checked: textTag-18.1 is successfully tested.
> It is Windows 10 1803

How strange. I remember that Ashok confirmed in the above ticket that 
Win10 1803 (so the April 2018 version) did NOT fix this. Could Ashok 
perhaps confirm again his findings?

> Maybe, there was a hotfix or we changed
> something, I don't know.

Hmm... I would feel more comfortable if we knew what made this test 
suddenly pass.

Checking the Tk side of things is easy: just bisect between The Tk 
version at the time the Falls Creator update went in, and the current Tk 
version.
A good candidate for what we changed is [745b43440b2cbe03], that fixed 
[e20d5ca7cd]. That one was for macOS, however this change (the added 
'update') could have fixed the Win10 case as well (however the 
workaround was to add 'after 50 ; update', not just 'update').

Checking the Win10 side of changes looks more difficult to me. However, 
Ashok in his analysis of the ticket found the root cause for the 
failure, and that was in a Windows API call (SetCursorPos) that changes 
with the Falls Creator Update version of Win 10. Quoting Ashok: "what 
seems to be happening is that the SetCursorPos call which triggers the 
Windows WM_MOVEMOUSE message does so after some delay in Windows 10 
compared to earlier versions".
This problem triggered several reports from users/developers of other 
applications than Tcl/Tk (Ashok gave the links in the ticket), we could 
probably check whether these issues are fixed, indicating the root cause 
that is common with Tk is fixed or not.

Regards,
Francois