|
From: Harald O. <har...@el...> - 2019-10-06 10:00:28
|
Am 05.10.2019 um 15:58 schrieb Francois Vogel:
> Le 05/10/2019 à 15:07, Harald Oehlmann a écrit :
>> Tk compilation:
>> All this is caused by the line:
>> DEBUG(unsigned owned:1); /* For debugging purposes. */
>> If I comment it out, it compiles well.
>
> Try building with the following line instead:
>
> DEBUG(unsigned owned:1;) /* For debugging purposes. */
>
> It should work.
Yes, it does, thank you.
>> ==== 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.
I can only say, that I did not move the mouse while testing. But the tcl
tests were running in parallel.
Thank you,
Harald
|