|
From: Francois V. <fvo...@fr...> - 2019-10-11 20:37:11
|
Le 06/10/2019 à 11:59, Harald Oehlmann a écrit :
> Am 05.10.2019 um 15:58 schrieb Francois Vogel:
>>> ==== bind-34.2 -warp works relatively to the screen FAILED
>>> ==== Contents of test case:
>>>
>>> # Contrary to bind-32.2, we're directly checking screen coordinates
>>> event generate {} <Motion> -x 20 -y 20 -warp 1
>>> update idletasks ; # DoWarp is an idle callback
>>> set res [winfo pointerxy .]
>>> event generate {} <Motion> -x 200 -y 200 -warp 1
>>> update idletasks ; # DoWarp is an idle callback
>>> lappend res {*}[winfo pointerxy .]
>>>
>>> ---- Result was:
>>> 20 19 200 200
>>> ---- Result should have been (exact matching):
>>> 20 20 200 200
>>> ==== bind-34.2 FAILED
>> So the pointer coordinates are erroneously (20,19) when warping to
>> (20,20), but they are correctly (200,200), when warping to (200,200)?
>> There is a difference of 1 unit, in y only, but not always. How come...?
>> That's strange. I don't reproduce this failure on my Vista system but I
>> will think about this.
Harald could you please try this again?
We now have a fix I think. It was for bind-34.1 that failed on Jan's
side, but that fix should also fix your failure with bind-34.2.
For this testing please use the tip of core-8-6-branch (at the time of
this writing the fix is not yet in the rc branch).
Thanks,
Francois
> I can only say, that I did not move the mouse while testing. But the tcl
> tests were running in parallel.
>
> Thank you,
> Harald
|