Re: [TCLCORE] Tcl/Tk 8.6.10 Release Candidates

[Francois V. <fra...@gm...>]

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.

> Tcl Test
>
> Compared to Tcl8.6.9
>
> New failing tests (details below): http-4.14, winFCmd-6.1, winFCmd-6.9,
> winFCmd-6.13, winFCmd-9.3

The winFCmd failures were reported here:

https://core.tcl-lang.org/tcl/tktview/ad28319dc2b9ae9da28384c91bf371be50793d8c

Not yet addressed, not solved yet.

> Tk Test
>
> Compared to Tk8.6.9.
>
> New failing tests (details below): bind-34.2

This is a new test I have added when fixing textTag-18.1, see:

     https://core.tcl-lang.org/tk/info/cb870417882574bb

> Not failing any more: textTag-18.1

Expected since I have fixed it: 
https://core.tcl-lang.org/tk/tktview?name=69b48f427e

> ==== 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.

F.