Re: [TCLCORE] Notification of potential incompatibility for releases 8.6.15 (and possibly 9.0.0)

[Csaba N. <csa...@t-...>]

Am 10.09.24 um 02:24 schrieb Francois Vogel:
> Le 09/09/2024 à 23:05, Erik Leunissen a écrit :
>> On 9/9/24 22:19 , Francois Vogel wrote:
>>>
>>>> Nevertheless, Csaba Nemethi made adaptations to one of his packages 
>>>> because of this fix. 
>>> I would be interested to know what had to be adapted here (especially 
>>> considering that Csaba tested the changes before we merged).
>>
>> Please see the 5th entry in this changes file:
>>
>> What is new in Tablelist 7.3?
> 
> Found!
> 
> https://core.tcl-lang.org/tklib/info/8eee6fc51de614e3
> 
> Unfortunately this is a large commit with all the changes from Tablelist 
> 7.2 to 7.3, not just the adaptation of Tablelist to the Tk change we're 
> discussing now. I think the relevant part of this commit is what changed 
> in lines 911-918 of modules/tablelist/scripts/tablelistBind.tcl, along 
> with two lines removal in modules/tablelist/scripts/tablelistWidget.tcl. 
> Perhaps the only relevant part is the check on  if {"%d" ne 
> "NotifyInferior"} {...
> 
> In the meantime I see that Don has added a
> 
>          *** POTENTIAL INCOMPATIBILITY ***
> 
> line in the changes file of core-8-6-15-rc, which should close the case 
> I think.
> 
> Regards,
> 
> Francois
> 
> 
> 
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core


Yes, I tested those changes before the merge, but several weeks later I 
discovered that a <FocusOut> event with the detail field 
"NotifyInferior" caused a minor asymmetry related to the appearance of 
the active tablelist row or cell:  By starting the interactive editing 
of a cell's content, the black rectangle around the active row or cell 
disappeared due to the <FocusOut> event with %d = "NotifyInferior"; by 
clicking somewhere on the desktop still during the editing session and 
then on the toplevel containing the tablelist widget, that rectangle 
became visible again.  Not a big deal, but it was easy to eliminate this 
minor issue by checking the detail field of the <FocusOut> event.

Best regards,

Csaba

-- 
Csaba Nemethi  https://www.nemethi.de  mailto:csa...@t-...