tcl-core — Tcl Core Team discussions about Tcl development

Re: [TCLCORE] Tcl 9.0.2 Release Candidate

[<apn...@ya...>]

The Windows exec-bug-4f0b5767ac error Paul reports can probably be ignored. The test constraint checks for presence of the winget file but not whether it is on the PATH. My guess is the MSYS environment Paul is running scrubs the Windows PATH and therefore does not find winget.

I've tested Tcl Windows 10+VS 2022 x64 combinations of shared, static, with and without embedded zipfs. Same results as Paul except for the winget failure which I don't see.

For Tk, have only tested the shared build so far and I see the usual 3 clipboard test failures (clipboard cannot be opened, another application grabbed it) that have been present on my system since 8.6 and can be ignored. I have never been able to figure out what application is grabbing the clipboard.

/Ashok

-----Original Message-----
From: Paul Obermeier <pa...@po...> 
Sent: Friday, June 27, 2025 11:21 PM
To: tcl...@li...
Subject: Re: [TCLCORE] Tcl 9.0.2 Release Candidate

Here are the results of the Tcl 9.0.2 test suite using my BAWT build environments.
No show-stoppers detected.

Operating system        Arch. Compiler Errors
-----------------------------------------------------
MacOS 15.5              M2      clang 17.0.0    0
Suse 15.6               x64     gcc 7.5.0       0
Raspberry Pi OS         arm64   gcc 12.2.0      0
Debian (StarFive)       RiscV   gcc 12.2.0      1
Windows 11              x86     gcc 7.2.0       4
Windows 11              x64     gcc 7.2.0       4
Windows 11              x64     VS2022          4

Windows tests include the usual 3 failures:
==== fCmd-9.3 file rename: comprehensive: file to new name FAILED
==== fCmd-9.10 file rename: comprehensive: file to new name and dir FAILED
==== winFCmd-3.10 TclpDeleteFile: path is readonly FAILED

Additional bug when running tests on Windows using MSys environment:

==== exec-bug-4f0b5767ac exec App Execution Alias FAILED
==== Contents of test case:

     exec winget --info

---- Test generated error; Return code was: 1
---- Return code should have been one of: 0 2
---- errorInfo: couldn't execute "winget": no such file or directory
     while executing
"exec winget --info"
     ("uplevel" body line 2)
     invoked from within
"uplevel 1 $script"
---- errorCode: POSIX ENOENT {no such file or directory}
==== exec-bug-4f0b5767ac FAILED

StarFive failure (was already in Tcl 9.0.0):

==== binary-40.3 ScanNumber: NaN FAILED
==== Contents of test case:

     unset -nocomplain arg1
     list [binary scan \xFF\xFF\xFF\xFF f1 arg1] $arg1

---- Result was:
1 NaN
---- Result should have been (glob matching):
1 -NaN*
==== binary-40.3 FAILED

Am 26.06.2025 um 20:15 schrieb Donald G Porter via Tcl-Core:
>
> Now available at
>
> https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/
>
> is an RC0 candidate source code distribution pre-release of Tcl 9.0.2
>
> This is the first candidate release leading to the release of Tcl 9.0.2. Testing of builds
> and operations on multiple platforms is invited.  Any critical problem that should block
> the release should be reported immediately.
>
> The Tcl pre-release includes pre-releases of the packages Itcl 4.3.3, Thread 3.0.2,
> and TDBC* 1.1.11.  The same level of vetting on them is also appreciated.  The
> released package sqlite 3.49.1 is also included.
>
> Release notes are under development, and will be available in an RC1 release to follow.
>
> Thank you for your contributions and assistance.
>



_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] Tk 9.0.2 Release Candidate

[Paul O. <pa...@po...>]

Here are the results of the Tk 9.0.2 test suite using my BAWT build environments.
No show-stoppers detected.

Operating system        Arch. Compiler Errors
-----------------------------------------------------
MacOS 15.5              M2      clang 17.0.0    0
Suse 15.6               x64     gcc 7.5.0      60
Raspberry Pi OS         arm64   gcc 12.2.0     64
Debian (StarFive)       RiscV   gcc 12.2.0     39
Windows 11              x86     gcc 7.2.0       0
Windows 11              x64     gcc 7.2.0       0
Windows 11              x64     VS2022          0

Note, that Windows and Mac tests were executed on laptops.
To get zero failures, the system scaling had to be set to 100 %.

Paul

Am 26.06.2025 um 20:16 schrieb Donald G Porter via Tcl-Core:
>
> Now available at
>
> https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/
>
> is an RC0 candidate source code distribution pre-release of Tk 9.0.2
>
> This is the first candidate release leading to the release of Tk 9.0.2. Testing of builds
> and operations on multiple platforms is invited.  Any critical problem that should block
> the release should be reported immediately.
>
> Release notes are under development, and will be available in an RC1 release to follow.
>
> Thank you for your contributions and assistance.
>

Re: [TCLCORE] Tcl 9.0.2 Release Candidate

[Paul O. <pa...@po...>]

Here are the results of the Tcl 9.0.2 test suite using my BAWT build environments.
No show-stoppers detected.

Operating system        Arch. Compiler Errors
-----------------------------------------------------
MacOS 15.5              M2      clang 17.0.0    0
Suse 15.6               x64     gcc 7.5.0       0
Raspberry Pi OS         arm64   gcc 12.2.0      0
Debian (StarFive)       RiscV   gcc 12.2.0      1
Windows 11              x86     gcc 7.2.0       4
Windows 11              x64     gcc 7.2.0       4
Windows 11              x64     VS2022          4

Windows tests include the usual 3 failures:
==== fCmd-9.3 file rename: comprehensive: file to new name FAILED
==== fCmd-9.10 file rename: comprehensive: file to new name and dir FAILED
==== winFCmd-3.10 TclpDeleteFile: path is readonly FAILED

Additional bug when running tests on Windows using MSys environment:

==== exec-bug-4f0b5767ac exec App Execution Alias FAILED
==== Contents of test case:

     exec winget --info

---- Test generated error; Return code was: 1
---- Return code should have been one of: 0 2
---- errorInfo: couldn't execute "winget": no such file or directory
     while executing
"exec winget --info"
     ("uplevel" body line 2)
     invoked from within
"uplevel 1 $script"
---- errorCode: POSIX ENOENT {no such file or directory}
==== exec-bug-4f0b5767ac FAILED

StarFive failure (was already in Tcl 9.0.0):

==== binary-40.3 ScanNumber: NaN FAILED
==== Contents of test case:

     unset -nocomplain arg1
     list [binary scan \xFF\xFF\xFF\xFF f1 arg1] $arg1

---- Result was:
1 NaN
---- Result should have been (glob matching):
1 -NaN*
==== binary-40.3 FAILED

Am 26.06.2025 um 20:15 schrieb Donald G Porter via Tcl-Core:
>
> Now available at
>
> https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/
>
> is an RC0 candidate source code distribution pre-release of Tcl 9.0.2
>
> This is the first candidate release leading to the release of Tcl 9.0.2. Testing of builds
> and operations on multiple platforms is invited.  Any critical problem that should block
> the release should be reported immediately.
>
> The Tcl pre-release includes pre-releases of the packages Itcl 4.3.3, Thread 3.0.2,
> and TDBC* 1.1.11.  The same level of vetting on them is also appreciated.  The
> released package sqlite 3.49.1 is also included.
>
> Release notes are under development, and will be available in an RC1 release to follow.
>
> Thank you for your contributions and assistance.
>

Re: [TCLCORE] Tk 9.0.2 Release Candidate

[<apn...@ya...>]

Fixed the test to just check Windows*. Any further detail might just cause test failures
in other locales. Also, the actual text is really not important as the test is to ensure exec
handles app execution aliases correctly. Failures are detected by error exceptions.

-----Original Message-----
From: Paul Obermeier <pa...@po...> 
Sent: Friday, June 27, 2025 3:52 AM
To: tcl...@li...
Subject: Re: [TCLCORE] Tk 9.0.2 Release Candidate

Quick comments on the reported Windows failures:
1. winget failure: Maybe a "Windows*Manager*" match would be better than just "Windows*".
2. Tk failures: I do not get any failures, if scaling is set to 100%.

More results regarding the platforms supported by BAWT presumably tomorrow.

Paul


Am 26.06.2025 um 23:13 schrieb Harald Oehlmann:
> Am 26.06.2025 um 20:16 schrieb Donald G Porter via Tcl-Core:
>>
>> Now available at
>>
>> https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/
>>
>> is an RC0 candidate source code distribution pre-release of Tk 9.0.2
> Thanks, great. Here is the test result with:
> MS-WIN 11 64bit GER,MS-VS2022.
>
> TCL&Tk&bundled packages:Build and install: clean
> Test with large application: ok
>
> Test suite:
> TCL: only test exec-bug-4f0b5767ac fails.
>
> This is due to a localization issue.
> The winget returns a German message, while the test result expects an English one, see below. Probably, only the word "Windows" may be tested...
>
> ==== exec-bug-4f0b5767ac exec App Execution Alias FAILED
> ==== Contents of test case:
>
>     exec winget --info
>
> ---- Result was:
> Windows-Paket-Manager v1.11.400
> ...
> ---- Result should have been (glob matching):
> Windows Package Manager*
> ==== exec-bug-4f0b5767ac FAILED
>
> Tk test is more complicated.
> I had to press the enter button in one dialog test and there was a bg error message box. 18 tests failed.
> I suppose, I am working on my laptop in a hotel and the scaling factor is quite custom. The scaling is set in the windows system to 150%.
>
> The test report is as follows:
>
> ==== frame-12.3 FrameWorldChanged procedure FAILED
> ==== Contents of test case:
>
>     # Check reaction on font change
>     font create myfont -family courier -size 10
>     labelframe .f -font myfont -text Mupp
>     place .f -x 0 -y 0 -width 40 -height 40
>     pack [frame .f.f] -fill both -expand 1
>     update
>     set h1 [font metrics myfont -linespace]
>     set y1 [winfo y .f.f]
>     font configure myfont -size 20
>     update  ; # services the "TheWorldHasChanged" event, queues "TkWorldChanged" events
>     update  ; # services the queued "TkWorldChanged" events
>     set h2 [font metrics myfont -linespace]
>     set y2 [winfo y .f.f]
>     expr {($h2 - $h1) - ($y2 - $y1)}
>
> ---- Result was:
> 20
> ---- Result should have been (exact matching):
> 0
> ==== frame-12.3 FAILED
>
> ==== frame-14.1 labelframe labelwidget option FAILED
> ==== Contents of test case:
>
>     # Test that label is moved in stacking order
>     label .l -text Mupp -font {helvetica 8}
>     labelframe .f -labelwidget .l
>     pack .f
>     frame .f.f -width 50 -height 50
>     pack .f.f
>     update
>     list [winfo children .] [winfo width .f]  [expr {[winfo height .f] - [winfo height .l]}]
>
> ---- Result was:
> {.f .l} 57 52
> ---- Result should have been (exact matching):
> {.f .l} 54 52
> ==== frame-14.1 FAILED
>
> ==== grid-16.11 layout uniform (shrink) FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 75 -height 50
>     frame .f2 -width 100 -height 95
>     grid .f1 .f2 -sticky news
>     grid columnconfigure . {0 1} -uniform a
>     grid columnconfigure . 0 -weight 1
>     update
>     set res {}
>     lappend res [grid bbox . 0 0] [grid bbox . 1 0]
>     grid propagate . 0
>     . configure -width 150 -height 95
>     update
>     lappend res [grid bbox . 0 0] [grid bbox . 1 0]
>
> ---- Result was:
> {0 0 100 95} {100 0 100 95} {0 0 76 95} {76 0 100 95}
> ---- Result should have been (exact matching):
> {0 0 100 95} {100 0 100 95} {0 0 50 95} {50 0 100 95}
> ==== grid-16.11 FAILED
>
> ==== grid-16.13 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 24 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     grid .f1 - - .f2
>     grid .f3 - - -
>     set res {}
>     foreach w {{0 1 0 0} {0 0 1 0} {1 3 4 0} {1 2 1 2} {1 1 1 12}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>     # The last result below should ideally be 8 8 8 126 but the current
>     # implementation is not exact enough.
>
> ---- Result was:
> {0 138 0 38 0} {0 0 138 38 0} {17 52 69 38 0} {22 47 22 85 0} {8 10 11 147 0}
> ---- Result should have been (exact matching):
> {0 112 0 38 0} {0 0 112 38 0} {14 42 56 38 0} {18 38 18 76 0} {7 8 9 126 0}
> ==== grid-16.13 FAILED
>
> ==== grid-16.14 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 110 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     grid .f1 - - .f2
>     grid .f3 - - -
>     set res {}
>     foreach w {{0 1 0 0} {0 0 1 0} {1 3 4 0} {1 2 1 3} {1 1 1 12}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>
> ---- Result was:
> {0 138 0 38 0} {0 0 138 38 0} {17 52 69 38 0} {30 63 31 52 0} {37 39 39 61 0}
> ---- Result should have been (exact matching):
> {0 112 0 38 0} {0 0 112 38 0} {14 42 56 38 0} {27 55 28 40 0} {36 37 37 40 0}
> ==== grid-16.14 FAILED
>
> ==== grid-16.15 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 24 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     grid .f1 - - .f2
>     grid x .f3 - -
>     set res {}
>     foreach w {{0 1 0 0} {0 0 1 0} {1 0 1 0} {0 0 0 0} {1 0 0 6}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>
> ---- Result was:
> {0 138 0 38 0} {0 0 138 38 0} {13 0 125 38 0} {0 37 37 76 0} {3 12 12 149 0}
> ---- Result should have been (exact matching):
> {0 112 0 38 0} {0 0 112 38 0} {0 0 112 38 0} {0 37 37 76 0} {0 12 12 126 0}
> ==== grid-16.15 FAILED
>
> ==== grid-16.16 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 64 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     frame .f4 -width 15 -height 20
>     frame .f5 -width 18 -height 20
>     frame .f6 -width 20 -height 20
>     grid .f1 - x .f2
>     grid .f3 - - -
>     grid .f4 .f5 .f6
>     set res {}
>     foreach w {{1 1 5 1} {0 0 1 0} {1 3 4 0} {1 2 1 2} {1 1 1 12}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>
> ---- Result was:
> {33 37 59 47 0} {30 34 74 38 0} {25 52 61 38 0} {29 48 33 66 0} {31 36 24 85 0}
> ---- Result should have been (exact matching):
> {30 34 43 43 0} {30 34 48 38 0} {22 42 48 38 0} {25 39 29 57 0} {30 34 22 64 0}
> ==== grid-16.16 FAILED
>
> ==== grid-18.2 test support for minreqsize FAILED
> ==== Contents of test case:
>
>     toplevel .pack
>     wm geometry .pack {}
>     frame .pack.l -width 150 -height 100
>     labelframe .pack.lf -labelwidget .pack.l
>     pack .pack.lf -fill both -expand 1
>     frame .pack.lf.f -width 20 -height 25
>     grid .pack.lf.f
>     update
>     set res [list [winfo geometry .pack.lf]]
>     .pack.lf configure -labelanchor ws
>     update
>     lappend res [winfo geometry .pack.lf]
>     destroy .pack
>     return $res
>
> ---- Result was:
> 176x127+0+0 176x112+0+0
> ---- Result should have been (exact matching):
> 162x127+0+0 172x112+0+0
> ==== grid-18.2 FAILED
>
> ==== pack-19.2 test support for minreqsize FAILED
> ==== Contents of test case:
>
>     wm geometry .pack {}
>     frame .pack.l -width 150 -height 100
>     labelframe .pack.lf -labelwidget .pack.l
>     pack .pack.lf -fill both -expand 1
>     frame .pack.lf.f -width 20 -height 25
>     pack .pack.lf.f
>     update
>     set res [list [winfo geometry .pack.lf]]
>     .pack.lf configure -labelanchor ws
>     update
>     lappend res [winfo geometry .pack.lf]
>
> ---- Result was:
> 176x127+0+0 176x112+0+0
> ---- Result should have been (exact matching):
> 162x127+0+0 172x112+0+0
> ==== pack-19.2 FAILED
>
> ==== scrollbar-3.35 ScrollbarWidgetCmd procedure, "fraction" option FAILED
> ==== Contents of test case:
>
>     format {%.6g} [.s fraction 4 21]
>
> ---- Result was:
> 0
> ---- Result should have been (exact matching):
> -0.0340136
> ==== scrollbar-3.35 FAILED
>
> ==== scrollbar-3.36 ScrollbarWidgetCmd procedure, "fraction" option FAILED
> ==== Contents of test case:
>
>     format {%.6g} [.s fraction 4 179]
>
> ---- Result was:
> 1
> ---- Result should have been (exact matching):
> 1.04082
> ==== scrollbar-3.36 FAILED
>
> ==== scrollbar-3.38 ScrollbarWidgetCmd procedure, "fraction" option FAILED
> ==== Contents of test case:
>
>     format {%.6g} [.s fraction 4 178]
>
> ---- Result was:
> 1
> ---- Result should have been (exact matching):
> 1.03401
> ==== scrollbar-3.38 FAILED
>
> ==== scrollbar-6.27 ScrollbarPosition procedure FAILED
> ==== Contents of test case:
>
>     .s identify [expr {[winfo width .s] / 2}] [expr {int(.4 / [.s delta 0 1])
>                          + [testmetrics cyvscroll .s]}]
>
> ---- Result was:
> slider
> ---- Result should have been (exact matching):
> trough2
> ==== scrollbar-6.27 FAILED
>
> ==== textImage-4.2 alignment checking - baseline FAILED
> ==== Contents of test case:
>
>     catch {
>     image create photo small -width 5 -height 5
>     small put red -to 0 0 4 4
>     image create photo large -width 50 -height 50
>     large put green -to 0 0 50 50
>     }
>     font create test_font2 -size 5
>     text .t -font test_font2 -bd 0 -highlightthickness 0 -padx 0 -pady 0
>     pack .t
>     .t image create end -image large
>     .t image create end -image small -align baseline
>     .t insert end test
>     update
>     # Sizes larger than 25 can be too big and lead to a negative 'norm',
>     # at least on Windows XP with certain settings.
>     foreach size {10 15 20 25} {
>     font configure test_font2 -size $size
>     array set Metrics [font metrics test_font2]
>     update  ; # services the idle "TheWorldHasChanged" event, queues "TkWorldChanged" events
>     update  ; # services the queued "TkWorldChanged" events
>     foreach {x y w h} [.t bbox small] {}
>     set norm [expr {
>         (([image height large] - $Metrics(-linespace))/2
>         + $Metrics(-ascent) - [image height small] - $y)
>     }]
>     lappend result "$size $norm"
>     }
>     return $result
>
> ---- Result was:
> {10 0} {15 0} {20 0} {25 -4}
> ---- Result should have been (exact matching):
> {10 0} {15 0} {20 0} {25 0}
> ==== textImage-4.2 FAILED
>
> ==== winDialog-5.16 GetFileName: parent FAILED
> ==== Contents of test case:
>
> #        case FILE_PARENT:
>
>     toplevel .t
>     set x 0
>     testDialog launch {tk_getOpenFile -parent .t -title Parent; set x 1}
>     testDialog onDisplay {
>     destroy .t
>     }
>     return $x
>
> ---- Result was:
> 0
> ---- Result should have been (exact matching):
> 1
> ==== winDialog-5.16 FAILED
>
> ==== winWm-2.4 TkpWmSetState FAILED
> ==== Contents of test case:
>
>     toplevel .t
>     wm geometry .t 150x50+10+10
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>     wm iconify .t
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>     wm geometry .t 200x50+10+10
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>     wm deiconify .t
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>
> ---- Result was:
> {normal 176x50+10+10} {iconic 176x50+10+10} {iconic 176x50+10+10} {normal 200x50+10+10}
> ---- Result should have been (exact matching):
> {normal 150x50+10+10} {iconic 150x50+10+10} {iconic 150x50+10+10} {normal 200x50+10+10}
> ==== winWm-2.4 FAILED
>
> ==== winWm-5.1 UpdateGeometryInfo: menu resizing FAILED
> ==== Contents of test case:
>
>     toplevel .t
>     frame .t.f -width 150 -height 50 -background red
>     pack .t.f
>     update
>     set result [winfo height .t]
>     menu .t.m
>     .t.m add command -label foo
>     .t configure -menu .t.m
>     update
>     lappend result [winfo height .t]
>     .t.m add command -label "thisisreallylong"
>     .t.m add command -label "thisisreallylong"
>     update
>     lappend result [winfo height .t]
>
> ---- Result was:
> 50 50 0
> ---- Result should have been (exact matching):
> 50 50 31
> ==== winWm-5.1 FAILED
>
> ==== wm-geometry-2.1 setting values FAILED
> ==== Contents of test case:
>
>     wm geometry .t 150x150+50+50
>     update
>     set result [wm geometry .t]
>     wm geometry .t {}
>     update
>     return [list $result [string equal [wm geometry .t] $result]]
>
> ---- Result was:
> 176x150+50+50 0
> ---- Result should have been (glob matching):
> 150x150+*+* 0
> ==== wm-geometry-2.1 FAILED
>
> Sorry,
> Harald
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core



_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] Bologna/Italy conference 9/10th of July program published, registration still open

[Torsten B. <be...@ty...>]

Hi,

yes, totally agree. This would also be good for a repeated announcement on Mastodon and X/Twitter, trying to get some more people to attend.


Torsten


> Am 26.06.2025 um 16:12 schrieb Colin Macleod via Tcl-Core <tcl...@li...>:
> 
> Hi, it's good to get this update.
> 
> But why is the program only accessible after logging in?  I have already posted reminders about the conference in a few places, e.g. https://www.linkedin.com/posts/colin-macleod-099a1713_last-chance-to-register-for-the-2025-openacs-activity-7343924691171962881-wY0d. I would like to update these reminders with a link to the program, but that's not possible if it's not publicly accessible.  In previous years the program was also made public while registration was still open.
> 
> Colin.
> 
> On 26/06/2025 14:54, Harald Oehlmann wrote:
>> Dear OpenACS/TCL/Tk enthusiasts,
>> 
>> the conference program is now online:
>> 
>> https://openacs.km.at/evaluate/org/129998253/courses/event_130001647/static/xolrn/schedule 
>> 
>> Please feel invited to the conference in Bologna/Italy 9th to 10th of July 2025. The registration is still open until next Monday:
>> 
>> https://openacs.km.at
>> 
>> Best regards,
>> Antonio, Gustaf, Bernd, Stefan and Harald
>> 
>> 
>> 
>> _______________________________________________
>> Tcl-Core mailing list
>> Tcl...@li...
>> https://lists.sourceforge.net/lists/listinfo/tcl-core
> 
> 
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] Tk 9.0.2 Release Candidate

[Paul O. <pa...@po...>]

Quick comments on the reported Windows failures:
1. winget failure: Maybe a "Windows*Manager*" match would be better than just "Windows*".
2. Tk failures: I do not get any failures, if scaling is set to 100%.

More results regarding the platforms supported by BAWT presumably tomorrow.

Paul


Am 26.06.2025 um 23:13 schrieb Harald Oehlmann:
> Am 26.06.2025 um 20:16 schrieb Donald G Porter via Tcl-Core:
>>
>> Now available at
>>
>> https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/
>>
>> is an RC0 candidate source code distribution pre-release of Tk 9.0.2
> Thanks, great. Here is the test result with:
> MS-WIN 11 64bit GER,MS-VS2022.
>
> TCL&Tk&bundled packages:Build and install: clean
> Test with large application: ok
>
> Test suite:
> TCL: only test exec-bug-4f0b5767ac fails.
>
> This is due to a localization issue.
> The winget returns a German message, while the test result expects an English one, see below. Probably, only the word "Windows" may be tested...
>
> ==== exec-bug-4f0b5767ac exec App Execution Alias FAILED
> ==== Contents of test case:
>
>     exec winget --info
>
> ---- Result was:
> Windows-Paket-Manager v1.11.400
> ...
> ---- Result should have been (glob matching):
> Windows Package Manager*
> ==== exec-bug-4f0b5767ac FAILED
>
> Tk test is more complicated.
> I had to press the enter button in one dialog test and there was a bg error message box. 18 tests failed.
> I suppose, I am working on my laptop in a hotel and the scaling factor is quite custom. The scaling is set in the windows system to 150%.
>
> The test report is as follows:
>
> ==== frame-12.3 FrameWorldChanged procedure FAILED
> ==== Contents of test case:
>
>     # Check reaction on font change
>     font create myfont -family courier -size 10
>     labelframe .f -font myfont -text Mupp
>     place .f -x 0 -y 0 -width 40 -height 40
>     pack [frame .f.f] -fill both -expand 1
>     update
>     set h1 [font metrics myfont -linespace]
>     set y1 [winfo y .f.f]
>     font configure myfont -size 20
>     update  ; # services the "TheWorldHasChanged" event, queues "TkWorldChanged" events
>     update  ; # services the queued "TkWorldChanged" events
>     set h2 [font metrics myfont -linespace]
>     set y2 [winfo y .f.f]
>     expr {($h2 - $h1) - ($y2 - $y1)}
>
> ---- Result was:
> 20
> ---- Result should have been (exact matching):
> 0
> ==== frame-12.3 FAILED
>
> ==== frame-14.1 labelframe labelwidget option FAILED
> ==== Contents of test case:
>
>     # Test that label is moved in stacking order
>     label .l -text Mupp -font {helvetica 8}
>     labelframe .f -labelwidget .l
>     pack .f
>     frame .f.f -width 50 -height 50
>     pack .f.f
>     update
>     list [winfo children .] [winfo width .f]  [expr {[winfo height .f] - [winfo height .l]}]
>
> ---- Result was:
> {.f .l} 57 52
> ---- Result should have been (exact matching):
> {.f .l} 54 52
> ==== frame-14.1 FAILED
>
> ==== grid-16.11 layout uniform (shrink) FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 75 -height 50
>     frame .f2 -width 100 -height 95
>     grid .f1 .f2 -sticky news
>     grid columnconfigure . {0 1} -uniform a
>     grid columnconfigure . 0 -weight 1
>     update
>     set res {}
>     lappend res [grid bbox . 0 0] [grid bbox . 1 0]
>     grid propagate . 0
>     . configure -width 150 -height 95
>     update
>     lappend res [grid bbox . 0 0] [grid bbox . 1 0]
>
> ---- Result was:
> {0 0 100 95} {100 0 100 95} {0 0 76 95} {76 0 100 95}
> ---- Result should have been (exact matching):
> {0 0 100 95} {100 0 100 95} {0 0 50 95} {50 0 100 95}
> ==== grid-16.11 FAILED
>
> ==== grid-16.13 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 24 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     grid .f1 - - .f2
>     grid .f3 - - -
>     set res {}
>     foreach w {{0 1 0 0} {0 0 1 0} {1 3 4 0} {1 2 1 2} {1 1 1 12}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>     # The last result below should ideally be 8 8 8 126 but the current
>     # implementation is not exact enough.
>
> ---- Result was:
> {0 138 0 38 0} {0 0 138 38 0} {17 52 69 38 0} {22 47 22 85 0} {8 10 11 147 0}
> ---- Result should have been (exact matching):
> {0 112 0 38 0} {0 0 112 38 0} {14 42 56 38 0} {18 38 18 76 0} {7 8 9 126 0}
> ==== grid-16.13 FAILED
>
> ==== grid-16.14 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 110 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     grid .f1 - - .f2
>     grid .f3 - - -
>     set res {}
>     foreach w {{0 1 0 0} {0 0 1 0} {1 3 4 0} {1 2 1 3} {1 1 1 12}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>
> ---- Result was:
> {0 138 0 38 0} {0 0 138 38 0} {17 52 69 38 0} {30 63 31 52 0} {37 39 39 61 0}
> ---- Result should have been (exact matching):
> {0 112 0 38 0} {0 0 112 38 0} {14 42 56 38 0} {27 55 28 40 0} {36 37 37 40 0}
> ==== grid-16.14 FAILED
>
> ==== grid-16.15 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 24 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     grid .f1 - - .f2
>     grid x .f3 - -
>     set res {}
>     foreach w {{0 1 0 0} {0 0 1 0} {1 0 1 0} {0 0 0 0} {1 0 0 6}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>
> ---- Result was:
> {0 138 0 38 0} {0 0 138 38 0} {13 0 125 38 0} {0 37 37 76 0} {3 12 12 149 0}
> ---- Result should have been (exact matching):
> {0 112 0 38 0} {0 0 112 38 0} {0 0 112 38 0} {0 37 37 76 0} {0 12 12 126 0}
> ==== grid-16.15 FAILED
>
> ==== grid-16.16 layout span FAILED
> ==== Contents of test case:
>
>     frame .f1 -width 64 -height 20
>     frame .f2 -width 38 -height 20
>     frame .f3 -width 150 -height 20
>     frame .f4 -width 15 -height 20
>     frame .f5 -width 18 -height 20
>     frame .f6 -width 20 -height 20
>     grid .f1 - x .f2
>     grid .f3 - - -
>     grid .f4 .f5 .f6
>     set res {}
>     foreach w {{1 1 5 1} {0 0 1 0} {1 3 4 0} {1 2 1 2} {1 1 1 12}} {
>     for {set c 0} {$c < 4} {incr c} {
>         grid columnconfigure . $c -weight [lindex $w $c]
>     }
>     update
>     set res2 {}
>     for {set c 0} {$c <= 4} {incr c} {
>         lappend res2 [lindex [grid bbox . $c 0] 2]
>     }
>     lappend res $res2
>     }
>     return $res
>
> ---- Result was:
> {33 37 59 47 0} {30 34 74 38 0} {25 52 61 38 0} {29 48 33 66 0} {31 36 24 85 0}
> ---- Result should have been (exact matching):
> {30 34 43 43 0} {30 34 48 38 0} {22 42 48 38 0} {25 39 29 57 0} {30 34 22 64 0}
> ==== grid-16.16 FAILED
>
> ==== grid-18.2 test support for minreqsize FAILED
> ==== Contents of test case:
>
>     toplevel .pack
>     wm geometry .pack {}
>     frame .pack.l -width 150 -height 100
>     labelframe .pack.lf -labelwidget .pack.l
>     pack .pack.lf -fill both -expand 1
>     frame .pack.lf.f -width 20 -height 25
>     grid .pack.lf.f
>     update
>     set res [list [winfo geometry .pack.lf]]
>     .pack.lf configure -labelanchor ws
>     update
>     lappend res [winfo geometry .pack.lf]
>     destroy .pack
>     return $res
>
> ---- Result was:
> 176x127+0+0 176x112+0+0
> ---- Result should have been (exact matching):
> 162x127+0+0 172x112+0+0
> ==== grid-18.2 FAILED
>
> ==== pack-19.2 test support for minreqsize FAILED
> ==== Contents of test case:
>
>     wm geometry .pack {}
>     frame .pack.l -width 150 -height 100
>     labelframe .pack.lf -labelwidget .pack.l
>     pack .pack.lf -fill both -expand 1
>     frame .pack.lf.f -width 20 -height 25
>     pack .pack.lf.f
>     update
>     set res [list [winfo geometry .pack.lf]]
>     .pack.lf configure -labelanchor ws
>     update
>     lappend res [winfo geometry .pack.lf]
>
> ---- Result was:
> 176x127+0+0 176x112+0+0
> ---- Result should have been (exact matching):
> 162x127+0+0 172x112+0+0
> ==== pack-19.2 FAILED
>
> ==== scrollbar-3.35 ScrollbarWidgetCmd procedure, "fraction" option FAILED
> ==== Contents of test case:
>
>     format {%.6g} [.s fraction 4 21]
>
> ---- Result was:
> 0
> ---- Result should have been (exact matching):
> -0.0340136
> ==== scrollbar-3.35 FAILED
>
> ==== scrollbar-3.36 ScrollbarWidgetCmd procedure, "fraction" option FAILED
> ==== Contents of test case:
>
>     format {%.6g} [.s fraction 4 179]
>
> ---- Result was:
> 1
> ---- Result should have been (exact matching):
> 1.04082
> ==== scrollbar-3.36 FAILED
>
> ==== scrollbar-3.38 ScrollbarWidgetCmd procedure, "fraction" option FAILED
> ==== Contents of test case:
>
>     format {%.6g} [.s fraction 4 178]
>
> ---- Result was:
> 1
> ---- Result should have been (exact matching):
> 1.03401
> ==== scrollbar-3.38 FAILED
>
> ==== scrollbar-6.27 ScrollbarPosition procedure FAILED
> ==== Contents of test case:
>
>     .s identify [expr {[winfo width .s] / 2}] [expr {int(.4 / [.s delta 0 1])
>                          + [testmetrics cyvscroll .s]}]
>
> ---- Result was:
> slider
> ---- Result should have been (exact matching):
> trough2
> ==== scrollbar-6.27 FAILED
>
> ==== textImage-4.2 alignment checking - baseline FAILED
> ==== Contents of test case:
>
>     catch {
>     image create photo small -width 5 -height 5
>     small put red -to 0 0 4 4
>     image create photo large -width 50 -height 50
>     large put green -to 0 0 50 50
>     }
>     font create test_font2 -size 5
>     text .t -font test_font2 -bd 0 -highlightthickness 0 -padx 0 -pady 0
>     pack .t
>     .t image create end -image large
>     .t image create end -image small -align baseline
>     .t insert end test
>     update
>     # Sizes larger than 25 can be too big and lead to a negative 'norm',
>     # at least on Windows XP with certain settings.
>     foreach size {10 15 20 25} {
>     font configure test_font2 -size $size
>     array set Metrics [font metrics test_font2]
>     update  ; # services the idle "TheWorldHasChanged" event, queues "TkWorldChanged" events
>     update  ; # services the queued "TkWorldChanged" events
>     foreach {x y w h} [.t bbox small] {}
>     set norm [expr {
>         (([image height large] - $Metrics(-linespace))/2
>         + $Metrics(-ascent) - [image height small] - $y)
>     }]
>     lappend result "$size $norm"
>     }
>     return $result
>
> ---- Result was:
> {10 0} {15 0} {20 0} {25 -4}
> ---- Result should have been (exact matching):
> {10 0} {15 0} {20 0} {25 0}
> ==== textImage-4.2 FAILED
>
> ==== winDialog-5.16 GetFileName: parent FAILED
> ==== Contents of test case:
>
> #        case FILE_PARENT:
>
>     toplevel .t
>     set x 0
>     testDialog launch {tk_getOpenFile -parent .t -title Parent; set x 1}
>     testDialog onDisplay {
>     destroy .t
>     }
>     return $x
>
> ---- Result was:
> 0
> ---- Result should have been (exact matching):
> 1
> ==== winDialog-5.16 FAILED
>
> ==== winWm-2.4 TkpWmSetState FAILED
> ==== Contents of test case:
>
>     toplevel .t
>     wm geometry .t 150x50+10+10
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>     wm iconify .t
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>     wm geometry .t 200x50+10+10
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>     wm deiconify .t
>     update
>     lappend result [list [wm state .t] [wm geometry .t]]
>
> ---- Result was:
> {normal 176x50+10+10} {iconic 176x50+10+10} {iconic 176x50+10+10} {normal 200x50+10+10}
> ---- Result should have been (exact matching):
> {normal 150x50+10+10} {iconic 150x50+10+10} {iconic 150x50+10+10} {normal 200x50+10+10}
> ==== winWm-2.4 FAILED
>
> ==== winWm-5.1 UpdateGeometryInfo: menu resizing FAILED
> ==== Contents of test case:
>
>     toplevel .t
>     frame .t.f -width 150 -height 50 -background red
>     pack .t.f
>     update
>     set result [winfo height .t]
>     menu .t.m
>     .t.m add command -label foo
>     .t configure -menu .t.m
>     update
>     lappend result [winfo height .t]
>     .t.m add command -label "thisisreallylong"
>     .t.m add command -label "thisisreallylong"
>     update
>     lappend result [winfo height .t]
>
> ---- Result was:
> 50 50 0
> ---- Result should have been (exact matching):
> 50 50 31
> ==== winWm-5.1 FAILED
>
> ==== wm-geometry-2.1 setting values FAILED
> ==== Contents of test case:
>
>     wm geometry .t 150x150+50+50
>     update
>     set result [wm geometry .t]
>     wm geometry .t {}
>     update
>     return [list $result [string equal [wm geometry .t] $result]]
>
> ---- Result was:
> 176x150+50+50 0
> ---- Result should have been (glob matching):
> 150x150+*+* 0
> ==== wm-geometry-2.1 FAILED
>
> Sorry,
> Harald
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] Tk 9.0.2 Release Candidate

[Harald O. <har...@el...>]

Am 26.06.2025 um 20:16 schrieb Donald G Porter via Tcl-Core:
> 
> Now available at
> 
> https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/
> 
> is an RC0 candidate source code distribution pre-release of Tk 9.0.2
Thanks, great. Here is the test result with:
MS-WIN 11 64bit GER,MS-VS2022.

TCL&Tk&bundled packages:Build and install: clean
Test with large application: ok

Test suite:
TCL: only test exec-bug-4f0b5767ac fails.

This is due to a localization issue.
The winget returns a German message, while the test result expects an 
English one, see below. Probably, only the word "Windows" may be tested...

==== exec-bug-4f0b5767ac exec App Execution Alias FAILED
==== Contents of test case:

     exec winget --info

---- Result was:
Windows-Paket-Manager v1.11.400
...
---- Result should have been (glob matching):
Windows Package Manager*
==== exec-bug-4f0b5767ac FAILED

Tk test is more complicated.
I had to press the enter button in one dialog test and there was a bg 
error message box. 18 tests failed.
I suppose, I am working on my laptop in a hotel and the scaling factor 
is quite custom. The scaling is set in the windows system to 150%.

The test report is as follows:

==== frame-12.3 FrameWorldChanged procedure FAILED
==== Contents of test case:

     # Check reaction on font change
     font create myfont -family courier -size 10
     labelframe .f -font myfont -text Mupp
     place .f -x 0 -y 0 -width 40 -height 40
     pack [frame .f.f] -fill both -expand 1
     update
     set h1 [font metrics myfont -linespace]
     set y1 [winfo y .f.f]
     font configure myfont -size 20
     update  ; # services the "TheWorldHasChanged" event, queues 
"TkWorldChanged" events
     update  ; # services the queued "TkWorldChanged" events
     set h2 [font metrics myfont -linespace]
     set y2 [winfo y .f.f]
     expr {($h2 - $h1) - ($y2 - $y1)}

---- Result was:
20
---- Result should have been (exact matching):
0
==== frame-12.3 FAILED

==== frame-14.1 labelframe labelwidget option FAILED
==== Contents of test case:

     # Test that label is moved in stacking order
     label .l -text Mupp -font {helvetica 8}
     labelframe .f -labelwidget .l
     pack .f
     frame .f.f -width 50 -height 50
     pack .f.f
     update
     list [winfo children .] [winfo width .f]  [expr {[winfo height .f] 
- [winfo height .l]}]

---- Result was:
{.f .l} 57 52
---- Result should have been (exact matching):
{.f .l} 54 52
==== frame-14.1 FAILED

==== grid-16.11 layout uniform (shrink) FAILED
==== Contents of test case:

     frame .f1 -width 75 -height 50
     frame .f2 -width 100 -height 95
     grid .f1 .f2 -sticky news
     grid columnconfigure . {0 1} -uniform a
     grid columnconfigure . 0 -weight 1
     update
     set res {}
     lappend res [grid bbox . 0 0] [grid bbox . 1 0]
     grid propagate . 0
     . configure -width 150 -height 95
     update
     lappend res [grid bbox . 0 0] [grid bbox . 1 0]

---- Result was:
{0 0 100 95} {100 0 100 95} {0 0 76 95} {76 0 100 95}
---- Result should have been (exact matching):
{0 0 100 95} {100 0 100 95} {0 0 50 95} {50 0 100 95}
==== grid-16.11 FAILED

==== grid-16.13 layout span FAILED
==== Contents of test case:

     frame .f1 -width 24 -height 20
     frame .f2 -width 38 -height 20
     frame .f3 -width 150 -height 20
     grid .f1 - - .f2
     grid .f3 - - -
     set res {}
     foreach w {{0 1 0 0} {0 0 1 0} {1 3 4 0} {1 2 1 2} {1 1 1 12}} {
	for {set c 0} {$c < 4} {incr c} {
	    grid columnconfigure . $c -weight [lindex $w $c]
	}
	update
	set res2 {}
	for {set c 0} {$c <= 4} {incr c} {
	    lappend res2 [lindex [grid bbox . $c 0] 2]
	}
	lappend res $res2
     }
     return $res
     # The last result below should ideally be 8 8 8 126 but the current
     # implementation is not exact enough.

---- Result was:
{0 138 0 38 0} {0 0 138 38 0} {17 52 69 38 0} {22 47 22 85 0} {8 10 11 
147 0}
---- Result should have been (exact matching):
{0 112 0 38 0} {0 0 112 38 0} {14 42 56 38 0} {18 38 18 76 0} {7 8 9 126 0}
==== grid-16.13 FAILED

==== grid-16.14 layout span FAILED
==== Contents of test case:

     frame .f1 -width 110 -height 20
     frame .f2 -width 38 -height 20
     frame .f3 -width 150 -height 20
     grid .f1 - - .f2
     grid .f3 - - -
     set res {}
     foreach w {{0 1 0 0} {0 0 1 0} {1 3 4 0} {1 2 1 3} {1 1 1 12}} {
	for {set c 0} {$c < 4} {incr c} {
	    grid columnconfigure . $c -weight [lindex $w $c]
	}
	update
	set res2 {}
	for {set c 0} {$c <= 4} {incr c} {
	    lappend res2 [lindex [grid bbox . $c 0] 2]
	}
	lappend res $res2
     }
     return $res

---- Result was:
{0 138 0 38 0} {0 0 138 38 0} {17 52 69 38 0} {30 63 31 52 0} {37 39 39 
61 0}
---- Result should have been (exact matching):
{0 112 0 38 0} {0 0 112 38 0} {14 42 56 38 0} {27 55 28 40 0} {36 37 37 
40 0}
==== grid-16.14 FAILED

==== grid-16.15 layout span FAILED
==== Contents of test case:

     frame .f1 -width 24 -height 20
     frame .f2 -width 38 -height 20
     frame .f3 -width 150 -height 20
     grid .f1 - - .f2
     grid x .f3 - -
     set res {}
     foreach w {{0 1 0 0} {0 0 1 0} {1 0 1 0} {0 0 0 0} {1 0 0 6}} {
	for {set c 0} {$c < 4} {incr c} {
	    grid columnconfigure . $c -weight [lindex $w $c]
	}
	update
	set res2 {}
	for {set c 0} {$c <= 4} {incr c} {
	    lappend res2 [lindex [grid bbox . $c 0] 2]
	}
	lappend res $res2
     }
     return $res

---- Result was:
{0 138 0 38 0} {0 0 138 38 0} {13 0 125 38 0} {0 37 37 76 0} {3 12 12 149 0}
---- Result should have been (exact matching):
{0 112 0 38 0} {0 0 112 38 0} {0 0 112 38 0} {0 37 37 76 0} {0 12 12 126 0}
==== grid-16.15 FAILED

==== grid-16.16 layout span FAILED
==== Contents of test case:

     frame .f1 -width 64 -height 20
     frame .f2 -width 38 -height 20
     frame .f3 -width 150 -height 20
     frame .f4 -width 15 -height 20
     frame .f5 -width 18 -height 20
     frame .f6 -width 20 -height 20
     grid .f1 - x .f2
     grid .f3 - - -
     grid .f4 .f5 .f6
     set res {}
     foreach w {{1 1 5 1} {0 0 1 0} {1 3 4 0} {1 2 1 2} {1 1 1 12}} {
	for {set c 0} {$c < 4} {incr c} {
	    grid columnconfigure . $c -weight [lindex $w $c]
	}
	update
	set res2 {}
	for {set c 0} {$c <= 4} {incr c} {
	    lappend res2 [lindex [grid bbox . $c 0] 2]
	}
	lappend res $res2
     }
     return $res

---- Result was:
{33 37 59 47 0} {30 34 74 38 0} {25 52 61 38 0} {29 48 33 66 0} {31 36 
24 85 0}
---- Result should have been (exact matching):
{30 34 43 43 0} {30 34 48 38 0} {22 42 48 38 0} {25 39 29 57 0} {30 34 
22 64 0}
==== grid-16.16 FAILED

==== grid-18.2 test support for minreqsize FAILED
==== Contents of test case:

     toplevel .pack
     wm geometry .pack {}
     frame .pack.l -width 150 -height 100
     labelframe .pack.lf -labelwidget .pack.l
     pack .pack.lf -fill both -expand 1
     frame .pack.lf.f -width 20 -height 25
     grid .pack.lf.f
     update
     set res [list [winfo geometry .pack.lf]]
     .pack.lf configure -labelanchor ws
     update
     lappend res [winfo geometry .pack.lf]
     destroy .pack
     return $res

---- Result was:
176x127+0+0 176x112+0+0
---- Result should have been (exact matching):
162x127+0+0 172x112+0+0
==== grid-18.2 FAILED

==== pack-19.2 test support for minreqsize FAILED
==== Contents of test case:

     wm geometry .pack {}
     frame .pack.l -width 150 -height 100
     labelframe .pack.lf -labelwidget .pack.l
     pack .pack.lf -fill both -expand 1
     frame .pack.lf.f -width 20 -height 25
     pack .pack.lf.f
     update
     set res [list [winfo geometry .pack.lf]]
     .pack.lf configure -labelanchor ws
     update
     lappend res [winfo geometry .pack.lf]

---- Result was:
176x127+0+0 176x112+0+0
---- Result should have been (exact matching):
162x127+0+0 172x112+0+0
==== pack-19.2 FAILED

==== scrollbar-3.35 ScrollbarWidgetCmd procedure, "fraction" option FAILED
==== Contents of test case:

     format {%.6g} [.s fraction 4 21]

---- Result was:
0
---- Result should have been (exact matching):
-0.0340136
==== scrollbar-3.35 FAILED

==== scrollbar-3.36 ScrollbarWidgetCmd procedure, "fraction" option FAILED
==== Contents of test case:

     format {%.6g} [.s fraction 4 179]

---- Result was:
1
---- Result should have been (exact matching):
1.04082
==== scrollbar-3.36 FAILED

==== scrollbar-3.38 ScrollbarWidgetCmd procedure, "fraction" option FAILED
==== Contents of test case:

     format {%.6g} [.s fraction 4 178]

---- Result was:
1
---- Result should have been (exact matching):
1.03401
==== scrollbar-3.38 FAILED

==== scrollbar-6.27 ScrollbarPosition procedure FAILED
==== Contents of test case:

     .s identify [expr {[winfo width .s] / 2}] [expr {int(.4 / [.s delta 
0 1])
						 + [testmetrics cyvscroll .s]}]

---- Result was:
slider
---- Result should have been (exact matching):
trough2
==== scrollbar-6.27 FAILED

==== textImage-4.2 alignment checking - baseline FAILED
==== Contents of test case:

     catch {
	image create photo small -width 5 -height 5
	small put red -to 0 0 4 4
	image create photo large -width 50 -height 50
	large put green -to 0 0 50 50
     }
     font create test_font2 -size 5
     text .t -font test_font2 -bd 0 -highlightthickness 0 -padx 0 -pady 0
     pack .t
     .t image create end -image large
     .t image create end -image small -align baseline
     .t insert end test
     update
     # Sizes larger than 25 can be too big and lead to a negative 'norm',
     # at least on Windows XP with certain settings.
     foreach size {10 15 20 25} {
	font configure test_font2 -size $size
	array set Metrics [font metrics test_font2]
	update  ; # services the idle "TheWorldHasChanged" event, queues 
"TkWorldChanged" events
	update  ; # services the queued "TkWorldChanged" events
	foreach {x y w h} [.t bbox small] {}
	set norm [expr {
		(([image height large] - $Metrics(-linespace))/2
		+ $Metrics(-ascent) - [image height small] - $y)
	}]
	lappend result "$size $norm"
     }
     return $result

---- Result was:
{10 0} {15 0} {20 0} {25 -4}
---- Result should have been (exact matching):
{10 0} {15 0} {20 0} {25 0}
==== textImage-4.2 FAILED

==== winDialog-5.16 GetFileName: parent FAILED
==== Contents of test case:

#        case FILE_PARENT:

     toplevel .t
     set x 0
     testDialog launch {tk_getOpenFile -parent .t -title Parent; set x 1}
     testDialog onDisplay {
	destroy .t
     }
     return $x

---- Result was:
0
---- Result should have been (exact matching):
1
==== winDialog-5.16 FAILED

==== winWm-2.4 TkpWmSetState FAILED
==== Contents of test case:

     toplevel .t
     wm geometry .t 150x50+10+10
     update
     lappend result [list [wm state .t] [wm geometry .t]]
     wm iconify .t
     update
     lappend result [list [wm state .t] [wm geometry .t]]
     wm geometry .t 200x50+10+10
     update
     lappend result [list [wm state .t] [wm geometry .t]]
     wm deiconify .t
     update
     lappend result [list [wm state .t] [wm geometry .t]]

---- Result was:
{normal 176x50+10+10} {iconic 176x50+10+10} {iconic 176x50+10+10} 
{normal 200x50+10+10}
---- Result should have been (exact matching):
{normal 150x50+10+10} {iconic 150x50+10+10} {iconic 150x50+10+10} 
{normal 200x50+10+10}
==== winWm-2.4 FAILED

==== winWm-5.1 UpdateGeometryInfo: menu resizing FAILED
==== Contents of test case:

     toplevel .t
     frame .t.f -width 150 -height 50 -background red
     pack .t.f
     update
     set result [winfo height .t]
     menu .t.m
     .t.m add command -label foo
     .t configure -menu .t.m
     update
     lappend result [winfo height .t]
     .t.m add command -label "thisisreallylong"
     .t.m add command -label "thisisreallylong"
     update
     lappend result [winfo height .t]

---- Result was:
50 50 0
---- Result should have been (exact matching):
50 50 31
==== winWm-5.1 FAILED

==== wm-geometry-2.1 setting values FAILED
==== Contents of test case:

     wm geometry .t 150x150+50+50
     update
     set result [wm geometry .t]
     wm geometry .t {}
     update
     return [list $result [string equal [wm geometry .t] $result]]

---- Result was:
176x150+50+50 0
---- Result should have been (glob matching):
150x150+*+* 0
==== wm-geometry-2.1 FAILED

Sorry,
Harald

[TCLCORE] Tcl 9.0.2 Release Candidate

[Donald G P. <don...@ni...>]

Now available at

https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/

is an RC0 candidate source code distribution pre-release of Tcl 9.0.2

This is the first candidate release leading to the release of Tcl 9.0.2. Testing of builds
and operations on multiple platforms is invited.  Any critical problem that should block
the release should be reported immediately.

The Tcl pre-release includes pre-releases of the packages Itcl 4.3.3, Thread 3.0.2,
and TDBC* 1.1.11.  The same level of vetting on them is also appreciated.  The
released package sqlite 3.49.1 is also included.

Release notes are under development, and will be available in an RC1 release to follow.

Thank you for your contributions and assistance.

-- 
| Don Porter            Applied and Computational Mathematics Division |
| don...@ni...             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

[TCLCORE] Tk 9.0.2 Release Candidate

[Donald G P. <don...@ni...>]

Now available at

https://sourceforge.net/projects/tcl/files/Tcl/9.0.2/

is an RC0 candidate source code distribution pre-release of Tk 9.0.2

This is the first candidate release leading to the release of Tk 9.0.2. Testing of builds
and operations on multiple platforms is invited.  Any critical problem that should block
the release should be reported immediately.

Release notes are under development, and will be available in an RC1 release to follow.

Thank you for your contributions and assistance.

-- 
| Don Porter            Applied and Computational Mathematics Division |
| don...@ni...             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

Re: [TCLCORE] Bologna/Italy conference 9/10th of July program published, registration still open

[Colin M. <col...@ya...>]

Hi, it's good to get this update.

But why is the program only accessible after logging in?  I have already 
posted reminders about the conference in a few places, e.g. 
https://www.linkedin.com/posts/colin-macleod-099a1713_last-chance-to-register-for-the-2025-openacs-activity-7343924691171962881-wY0d. 
I would like to update these reminders with a link to the program, but 
that's not possible if it's not publicly accessible.  In previous years 
the program was also made public while registration was still open.

Colin.

On 26/06/2025 14:54, Harald Oehlmann wrote:
> Dear OpenACS/TCL/Tk enthusiasts,
>
> the conference program is now online:
>
> https://openacs.km.at/evaluate/org/129998253/courses/event_130001647/static/xolrn/schedule 
>
>
> Please feel invited to the conference in Bologna/Italy 9th to 10th of 
> July 2025. The registration is still open until next Monday:
>
> https://openacs.km.at
>
> Best regards,
> Antonio, Gustaf, Bernd, Stefan and Harald
>
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core

[TCLCORE] TCL/Tk biweekly telco on 30 of June, 2025 12:00 UTC on https://meet.jit.si/TclMonthlyMeetup

[Harald O. <har...@el...>]

Dear Tcl/Tk team,

please allow me to invite anybody to the telco:
Where: https://meet.jit.si/TclMonthlyMeetup
When: 2025-06-30 12:00 UTC

Possible agenda:
1) Release items for TCL/Tk 9.0.2
Any blockers?

2) Release items for Tcl/Tk 9.1.0a0
What gets in?

3) TIP 649: list API for lreverse ....
4) TIP 700: documentation reform
5) TIP 726: unicode normalization
5) Conference status

Other meetings:
8th of July 1:00 UTC: TCL meetup on same Jitsi
14th of July 12:00 UTC: UTC Monthly Virtual Meetup on same jitsi

Thank you all,
Harald

[TCLCORE] Bologna/Italy conference 9/10th of July program published, registration still open

[Harald O. <har...@el...>]

Dear OpenACS/TCL/Tk enthusiasts,

the conference program is now online:

https://openacs.km.at/evaluate/org/129998253/courses/event_130001647/static/xolrn/schedule

Please feel invited to the conference in Bologna/Italy 9th to 10th of 
July 2025. The registration is still open until next Monday:

https://openacs.km.at

Best regards,
Antonio, Gustaf, Bernd, Stefan and Harald

Re: [TCLCORE] testutils.GUIDE in Tk 9.0.2

[Erik L. <el...@xs...>]

On 6/25/25 22:45 , Erik Leunissen via Tcl-Core wrote:
> So, to me I'd be strange if you encountered an exception for just one 
> file.
>
I'd be strange => it'd be strange


Erik.

Re: [TCLCORE] On editing whitespace

[Kevin W. <kw...@co...>]

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><img width="1" height="1" src="https://fedbdhd.r.tsp1-brevo.net/tr/op/FnIMzK7tL_B6Z-wEsu7LTvyFrZJUPIxpRuNG6bWHUtQkil7Pgk3MGyPhiYjT_OHfAzzWKvZpXiJR2v6fx6wE0YOZxPnvOOrGziEtNSJV9lfLiSS0AFzIf_NJvcBVx81n_HR0RrHDZZoPGT7NATKlMvEVe7FhAew3uItB9anQyzT1Zkma2EE8RB72APsh25g-E7OokDEQZ_dAm2xWNVLFBB5e0rOb" style="mso-hide:all"/><div dir="ltr"></div><div dir="ltr">I have a few recent commits in the tka11y accessibility branch with a ton of whitespace changes, among other major revisions. I trust that will be forgiven as the code is in a very volatile state and subject to lots of changes, and is a long way from being TIP-ready.&nbsp;</div><div dir="ltr"><br></div><div dir="ltr">—Kevin</div><div dir="ltr"><br><blockquote type="cite">On Jun 19, 2025, at 9:57 AM, Marc Culler &lt;cul...@gm...&gt; wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="auto">It is pretty disturbing to see a commit containing nothing but changes to whitespace after this discussion.<div dir="auto"><br></div><div dir="auto">- Marc</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Jun 18, 2025, 2:48 PM Francois Vogel &lt;<a href="mailto:fvo...@fr...">fvo...@fr...</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>

  
    
  
  <div>
    <p>It's comforting to observe that people's common views are being
      listened to.</p>
    <p>&nbsp;&nbsp;&nbsp;
<a href="https://fedbdhd.r.tsp1-brevo.net/tr/cl/7ZSgx9EDypWymGTk_GYo8OLJa2zjANIPrJyOx1CnBcCsMXPNEFvwvONJ4klCTqAjTQp-pFkSzkxt8Bg9zq_uuDJnIpuJ6BTJDFmy5Qqwrj1oLtBDtk812wX8Uu0NTx8BagbKmn0rKp4MbrtCrdjCTsS7YMb8Si6KdVYEDD_H0clHN9yDp_IgJdlpDZArTGTCoTHTMPyStVgC010kuV1uJ8kwYTI_ANrsKqOX-sw5JhfoaAf0sqv6dCtNtsQY4ksQUfIdXWdiEVd1Q_xe-buDpo1iaLNfpcjbFB021HhZrsaXZq8EbmmUx-Ow6OBAq1LTZoHBtLNXilo0RzPYTXVu-JiJKn3FNrzpkNgCbafHqS1ohElrY8YPS53Bhgk" target="_blank" rel="noreferrer">https://core.tcl-lang.org/tcl/info/40d70239582496f7b96a6024fa78bca461f5e3b94611d117414377d6f6f53c9b</a><br>
    </p>
    <p>Listen, this project will go on without me. I take a break (at
      least).<br>
    </p>
    <p>Francois<br>
    </p>
    <div>Le 04/06/2025 à 21:55, Francois Vogel a
      écrit&nbsp;:<br>
    </div>
    <blockquote type="cite">
      
      <p>Let me just state that I strongly second this exact request I
        have made a few times before (at no avail).</p>
      <p>Oh, and yes I know there is a switch in fossil allowing to
        ignore whitespaces in diffs. No, that does not make a true
        difference on the subject.</p>
      <p>Again: this is not about choosing between spaces and tabs. The
        Tcl engineering manual is clear about this (set TIP #247). It is
        about not changing what is already there, be it spaces or tabs.
        And this is true too for whitespace at end of lines.<br>
      </p>
      <p>Regards,</p>
      <p>Francois<br>
      </p>
      <div>Le 04/06/2025 à 18:24,
        apnmbx-public--- via Tcl-Core a écrit&nbsp;:<br>
      </div>
      <blockquote type="cite">
        
        
        
        <div>
          <p class="MsoNormal">On more than one occasion in the past
            couple of months, commits have been made that include
            copious changes of spaces to tabs. TIP 247, which presumably
            is the coding standard Tcl core follows, does not have any
            mandate to use tabs afaict. If that is the case, can we
            please desist from such changes? Without getting into a tabs
            vs spaces war (personally, I prefer spaces) can we just
            respect whatever exists as long as it meets the standard
            (indent of 4 etc.) It has practical implications in that,
            when reviewing diffs or merging, one has to go unnecessarily
            go through each diff to see what changed.<u></u><u></u></p>
          <p class="MsoNormal"><u></u>&nbsp;<u></u></p>
          <p class="MsoNormal">/Ashok<u></u><u></u></p>
        </div>
        <br>
        <fieldset></fieldset>
        <br>
        <fieldset></fieldset>
        <pre>_______________________________________________
Tcl-Core mailing list
<a href="mailto:Tcl...@li..." target="_blank" rel="noreferrer">Tcl...@li...</a>
<a href="https://fedbdhd.r.tsp1-brevo.net/tr/cl/TSmM85vDo84anDoGUxkhfRfDGFs7YaisN2eMX5F6pe6XtjnW4ddH0G9Oo-SngSoqcwyBHaXuOEIq0QlSYnUaTTjwYmY_4IEQI16lNAAZmgXsNVjcZeai_T7Pf8I-6xQnDl_w2CwjPdkjcwOFP-zlmGZtg7bsHWvUJytXRpo2qRMApIJZ6EooX4b-EbLenwfJO8WBgw14ZkTpKqpog_u3GmhzpKFdCogePiYJxBP4ctkQ1i0fmeoywsM_VUhDLY6wIxl5nFE-mwT8DPsCADWHNmoo_dEEXU4qCzmkhUWkLiCQbYev4MIdzIidLpsF0w" target="_blank" rel="noreferrer">https://lists.sourceforge.net/lists/listinfo/tcl-core</a>
</pre>
      </blockquote>
      <br>
      <fieldset></fieldset>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
Tcl-Core mailing list
<a href="mailto:Tcl...@li..." target="_blank" rel="noreferrer">Tcl...@li...</a>
<a href="https://fedbdhd.r.tsp1-brevo.net/tr/cl/_Hl_li9l-nAvELaSF6JnaSeg_dDN1-5AruPwx61C7au4u6-JnU3b-jiXmIjJScGLyPmrNR_UKLystHFUmH9WHvp0nEMaMIiXSap-q1lg4J-3x5WuVQao7BRkz7FoTj6ZkIvTDsOC9dXx0Cv8p4Dp0-vIXOdpy3UlWelUWGL_EX-yus7P_Jde28dhQDPb_KB9r4_4RNv-1sXWzDSWHEbnqNbH2pfsMNOOlUIXAqlEhhpAVdBEi0Tb1oRmR79LJhYZSrdGsk_zHWEOybXp8hJi2ByQzJN6EBfm9HRfIgDTtIZikBCJ8CvY_1KiOMlEkQ" target="_blank" rel="noreferrer">https://lists.sourceforge.net/lists/listinfo/tcl-core</a>
</pre>
    </blockquote>
  </div>

_______________________________________________<br>
Tcl-Core mailing list<br>
<a href="mailto:Tcl...@li..." target="_blank" rel="noreferrer">Tcl...@li...</a><br>
<a href="https://fedbdhd.r.tsp1-brevo.net/tr/cl/D30cxaZTX_OMqaAMO-8vcPSVpps5Y5HfipEoCFDDNguLKwu9uHD7Z87K8s3hGxgYtUD2cZCwQuhU25ndj3Q1bTN2SZLQWjsSykAWbDrKi4Zi-5J5ZhaRtZMqfR8HKo_O7PlJE5DYanHUE6bNZdGxJqNZH3LlQfHRJwUOH1iOWr3G6gbIw-TWW-qgVJRPkq8e2-NMdjdJev4pLOagltw_Is4FQpUJXluOAqRtyd4-lwfwZN0pul-qXyb7XwcLQ9I1mEtHirb4Eo0PJcF6LNy3rfFFIrEF75bZE9AXWdgYqMFtHrKCHJ_bbD9DhByO-Q" rel="noreferrer noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/tcl-core</a><br>
</blockquote></div>
<span>_______________________________________________</span><br><span>Tcl-Core mailing list</span><br><span>Tcl...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/tcl-core</span><br></div></blockquote></body></html>

Re: [TCLCORE] TkPath 0.4.1

[<apn...@ya...>]

Thanks Paul. I overlooked checking the demos. Committed a fix and they should be working now. Verified 9.0 and 8.6 with Ubuntu and 9.0 with VC++. Missed a structure field initializer during the merge though I’m not sure why it only impacted 9.0 and not 8.6.

 

Also, I noticed the TkPathItemType and TkPathCanvas structure no longer match the corresponding types in Tk. I presume that is ok since they are only used internally.

 

Hope someone will look at macos errors.

 

/Ashok

 

From: Paul Obermeier <pa...@po...> 
Sent: Thursday, June 26, 2025 1:22 AM
To: tcl...@li...
Subject: Re: [TCLCORE] TkPath 0.4.1

 

Thanks Ashok for caring.

I tested the tcltk-depot version on Windows (gcc), several Linux distros, Raspi and RiscV
using Tcl/Tk 8.6.16 and 9.0.1.
With the exception of MacOS the test suite runs without errors. 
On MacOS 15.5 there is 1 test suite error (both using 8.6.16 and 9.0.1), see below.
The demos work fine using 8.6.16, but do not work using 9.0.1.

I created issues for the 2 MacOS problems in case one of the Mac gurus
wants to take a closer look.

Regards,
Paul

Am 25.06.2025 um 17:30 schrieb apnmbx-public--- via Tcl-Core:

https://github.com/tcltk-depot/tkpath now (purportedly) holds the merge of all the tkpath forks, versioned 0.4.1. There were more diffs w.r.t. Paul’s 0.4.0 than I expected so it would be nice if someone reviewed the merge.

 

I’ve run the test suite on Windows 64 (VC++) and Ubuntu 20 (WSL). Volunteer needed to test on macOS (at least) and confirm.

 

I do not plan further work on it myself.

 

/Ashok

 

From: Paul Obermeier  <mailto:pa...@po...> <pa...@po...> 
Sent: Thursday, June 19, 2025 12:55 AM
To: apn...@ya... <mailto:apn...@ya...> ; tcl...@li... <mailto:tcl...@li...> 
Subject: Re: [TCLCORE] tclx, tktreectrl and tkpath repositories and a request

 

Some history.
I originally had Rene's tkpath version in BAWT (last update was in 2018),
which does not compile on Mac.
Manfred Rosenberger (author of tkpath based RattleCAD) asked me to add 
Christian Werner's version of tkpath, because his version runs on Mac and
has several other fixes.
After Tcl9 release Steve Shaw sent me a Tcl9 ready version of tkpath.
Unfortunately this version was based on Rene's version (no Mac) and did only
work with Tcl9, but not Tcl8.
I then merged the Tcl9 changes into Christian's version, which is the version 0.4.0
available with BAWT.

So in my point of view, the BAWT version is the most advanced one.
It runs the test suite without errors on Windows and Linux using Tcl/Tk 8.6.16 and Tcl/Tk 9.0.1
The test suite runs on Mac with 1 error both using Tcl/Tk 8.6.16 and 9.0.1, see below.

Paul

==== canvText-1.12 configuration options: bad value for -stipple FAILED
==== Contents of test case:

    .c create text 20 20 -tag test
    .c itemconfigure test $name $badValue

---- Test completed normally; Return code was: 0
---- Return code should have been one of: 1
==== canvText-1.12 FAILED




Am 18.06.2025 um 05:26 schrieb apnmbx-public--- via Tcl-Core:

Thanks Paul. Do you know if your version of tkpath also incorporates Rene’s changes from chiselapp?

 

I hope someone picks up tkpath, else I will make an attempt at a merge at some point. For the macOS issues, I’m afraid I have no way of testing GUI’s. At least for console only, Github actions can be used (painfully).

 

/Ashok

 

From: Paul Obermeier  <mailto:pa...@po...> <pa...@po...> 

I do have a version of tkpath, which is a merge of Christian's and Steve's work and compiles  
using Tcl 8.6 and 9.0 on Windows, Linux and Mac.
See https://www.bawt.tcl3d.org/download/InputLibs/tkpath-0.4.0.7z

It works on Windows and Linux using Tcl 8.6 and 9.0.
It works on Mac using 8.6, but does not work with Tcl 9.0.






tktreectrl and tkpath have been tested on Windows and Linux. Someone testing on macOS would be helpful.

Repository version of tktreectrl works on Windows, Linux, Mac using Tcl 8.6 and 9.0.

Note, that I tested the packages only by using the simple scripts contained in the BAWT framework.







_______________________________________________
Tcl-Core mailing list
Tcl...@li... <mailto:Tcl...@li...> 
https://lists.sourceforge.net/lists/listinfo/tcl-core

 






_______________________________________________
Tcl-Core mailing list
Tcl...@li... <mailto:Tcl...@li...> 
https://lists.sourceforge.net/lists/listinfo/tcl-core

 

Re: [TCLCORE] testutils.GUIDE in Tk 9.0.2

[Erik L. <el...@xs...>]

On 6/25/25 19:47 , Donald G Porter via Tcl-Core wrote:
>
> There is a new file in Tk since the release of Tk 9.0.1:
>
>     tk/tests/testutils.GUIDE
>
> It is not included in the source code distribution generated by `make 
> dist`.
>
> Should it be part of the Tk 9.0.2 release?
>
Hi Don,

That file is part of project tk_collect_test_utils (of which I am the 
author):

     https://core.tcl-lang.org/tk/tktview/718cbc3016

This project was merged into core-9-0-branch in commit 0318c8eab2 by Jan 
Nijtmans.
I don't feel that it's up to me whether to include it in Tk9.0.2, 
although that's very fine by me.

But I do want to point out that that project (and the merge into 
core-9-0-branch) introduced
four new files, not just one:

* tests/testutils.tcl

* tests/testutils.test

* tests/testutils.GUIDE

* tests/main.tcl

So, to me I'd be strange if you encountered an exception for just one file.

Regards,
Erik Leunissen.
--

Re: [TCLCORE] TkPath 0.4.1

[Paul O. <pa...@po...>]

Thanks Ashok for caring.

I tested the tcltk-depot version on Windows (gcc), several Linux distros, Raspi and RiscV
using Tcl/Tk 8.6.16 and 9.0.1.
With the exception of MacOS the test suite runs without errors.
On MacOS 15.5 there is 1 test suite error (both using 8.6.16 and 9.0.1), see below.
The demos work fine using 8.6.16, but do not work using 9.0.1.

I created issues for the 2 MacOS problems in case one of the Mac gurus
wants to take a closer look.

Regards,
Paul

Am 25.06.2025 um 17:30 schrieb apnmbx-public--- via Tcl-Core:
>
> https://github.com/tcltk-depot/tkpath now (purportedly) holds the merge of all the tkpath forks, versioned 0.4.1. There were more diffs w.r.t. Paul’s 0.4.0 than I expected so it would be nice if someone reviewed the merge.
>
> I’ve run the test suite on Windows 64 (VC++) and Ubuntu 20 (WSL). Volunteer needed to test on macOS (at least) and confirm.
>
> I do not plan further work on it myself.
>
> /Ashok
>
> *From:*Paul Obermeier <pa...@po...>
> *Sent:* Thursday, June 19, 2025 12:55 AM
> *To:* apn...@ya...; tcl...@li...
> *Subject:* Re: [TCLCORE] tclx, tktreectrl and tkpath repositories and a request
>
> Some history.
> I originally had Rene's tkpath version in BAWT (last update was in 2018),
> which does not compile on Mac.
> Manfred Rosenberger (author of tkpath based RattleCAD) asked me to add
> Christian Werner's version of tkpath, because his version runs on Mac and
> has several other fixes.
> After Tcl9 release Steve Shaw sent me a Tcl9 ready version of tkpath.
> Unfortunately this version was based on Rene's version (no Mac) and did only
> work with Tcl9, but not Tcl8.
> I then merged the Tcl9 changes into Christian's version, which is the version 0.4.0
> available with BAWT.
>
> So in my point of view, the BAWT version is the most advanced one.
> It runs the test suite without errors on Windows and Linux using Tcl/Tk 8.6.16 and Tcl/Tk 9.0.1
> The test suite runs on Mac with 1 error both using Tcl/Tk 8.6.16 and 9.0.1, see below.
>
> Paul
>
> ==== canvText-1.12 configuration options: bad value for -stipple FAILED
> ==== Contents of test case:
>
>     .c create text 20 20 -tag test
>     .c itemconfigure test $name $badValue
>
> ---- Test completed normally; Return code was: 0
> ---- Return code should have been one of: 1
> ==== canvText-1.12 FAILED
>
> Am 18.06.2025 um 05:26 schrieb apnmbx-public--- via Tcl-Core:
>
>     Thanks Paul. Do you know if your version of tkpath also incorporates Rene’s changes from chiselapp?
>
>     I hope someone picks up tkpath, else I will make an attempt at a merge at some point. For the macOS issues, I’m afraid I have no way of testing GUI’s. At least for console only, Github actions can be used (painfully).
>
>     /Ashok
>
>     *From:*Paul Obermeier <pa...@po...> <mailto:pa...@po...>
>
>     I do have a version of tkpath, which is a merge of Christian's and Steve's work and compiles
>     using Tcl 8.6 and 9.0 on Windows, Linux and Mac.
>     See https://www.bawt.tcl3d.org/download/InputLibs/tkpath-0.4.0.7z
>
>     It works on Windows and Linux using Tcl 8.6 and 9.0.
>     It works on Mac using 8.6, but does not work with Tcl 9.0.
>
>
>
>         tktreectrl and tkpath have been tested on Windows and Linux. Someone testing on macOS would be helpful.
>
>     Repository version of tktreectrl works on Windows, Linux, Mac using Tcl 8.6 and 9.0.
>
>     Note, that I tested the packages only by using the simple scripts contained in the BAWT framework.
>
>
>
>
>     _______________________________________________
>
>     Tcl-Core mailing list
>
>     Tcl...@li...
>
>     https://lists.sourceforge.net/lists/listinfo/tcl-core
>
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core

[TCLCORE] testutils.GUIDE in Tk 9.0.2

[Donald G P. <don...@ni...>]

There is a new file in Tk since the release of Tk 9.0.1:

     tk/tests/testutils.GUIDE

It is not included in the source code distribution generated by `make dist`.

Should it be part of the Tk 9.0.2 release?

-- 
| Don Porter            Applied and Computational Mathematics Division |
| don...@ni...             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

Re: [TCLCORE] TIP #649: Call for Votes

[Harald O. <har...@el...>]

Am 25.06.2025 um 03:27 schrieb apnmbx-public--- via Tcl-Core:
> This is a CFV for /TIP #649: Expose additional list functionality in the 
> C API/
> 
> Voting period ends 12PM UTC July 5^th .
> 
> /Ashok
Yes
Thanks,
Harald

[TCLCORE] TkPath 0.4.1

[<apn...@ya...>]

https://github.com/tcltk-depot/tkpath now (purportedly) holds the merge of all the tkpath forks, versioned 0.4.1. There were more diffs w.r.t. Paul’s 0.4.0 than I expected so it would be nice if someone reviewed the merge.

 

I’ve run the test suite on Windows 64 (VC++) and Ubuntu 20 (WSL). Volunteer needed to test on macOS (at least) and confirm.

 

I do not plan further work on it myself.

 

/Ashok

 

From: Paul Obermeier <pa...@po...> 
Sent: Thursday, June 19, 2025 12:55 AM
To: apn...@ya...; tcl...@li...
Subject: Re: [TCLCORE] tclx, tktreectrl and tkpath repositories and a request

 

Some history.
I originally had Rene's tkpath version in BAWT (last update was in 2018),
which does not compile on Mac.
Manfred Rosenberger (author of tkpath based RattleCAD) asked me to add 
Christian Werner's version of tkpath, because his version runs on Mac and
has several other fixes.
After Tcl9 release Steve Shaw sent me a Tcl9 ready version of tkpath.
Unfortunately this version was based on Rene's version (no Mac) and did only
work with Tcl9, but not Tcl8.
I then merged the Tcl9 changes into Christian's version, which is the version 0.4.0
available with BAWT.

So in my point of view, the BAWT version is the most advanced one.
It runs the test suite without errors on Windows and Linux using Tcl/Tk 8.6.16 and Tcl/Tk 9.0.1
The test suite runs on Mac with 1 error both using Tcl/Tk 8.6.16 and 9.0.1, see below.

Paul

==== canvText-1.12 configuration options: bad value for -stipple FAILED
==== Contents of test case:

    .c create text 20 20 -tag test
    .c itemconfigure test $name $badValue

---- Test completed normally; Return code was: 0
---- Return code should have been one of: 1
==== canvText-1.12 FAILED



Am 18.06.2025 um 05:26 schrieb apnmbx-public--- via Tcl-Core:

Thanks Paul. Do you know if your version of tkpath also incorporates Rene’s changes from chiselapp?

 

I hope someone picks up tkpath, else I will make an attempt at a merge at some point. For the macOS issues, I’m afraid I have no way of testing GUI’s. At least for console only, Github actions can be used (painfully).

 

/Ashok

 

From: Paul Obermeier  <mailto:pa...@po...> <pa...@po...> 

I do have a version of tkpath, which is a merge of Christian's and Steve's work and compiles  
using Tcl 8.6 and 9.0 on Windows, Linux and Mac.
See https://www.bawt.tcl3d.org/download/InputLibs/tkpath-0.4.0.7z

It works on Windows and Linux using Tcl 8.6 and 9.0.
It works on Mac using 8.6, but does not work with Tcl 9.0.





tktreectrl and tkpath have been tested on Windows and Linux. Someone testing on macOS would be helpful.

Repository version of tktreectrl works on Windows, Linux, Mac using Tcl 8.6 and 9.0.

Note, that I tested the packages only by using the simple scripts contained in the BAWT framework.






_______________________________________________
Tcl-Core mailing list
Tcl...@li... <mailto:Tcl...@li...> 
https://lists.sourceforge.net/lists/listinfo/tcl-core

 

Re: [TCLCORE] TIP #649: Call for Votes

[<apn...@ya...>]

And forgot to add my own vote.

 

TIP #649: YES

 

From: apn...@ya... <apn...@ya...> On Behalf Of
apn...@ya...
Sent: Wednesday, June 25, 2025 8:33 AM
To: apn...@ya...; tcl...@li...
Subject: RE: [TCLCORE] TIP #649: Call for Votes

 

Forgot to include a link to the TIP -
https://core.tcl-lang.org/tips/doc/trunk/tip/649.md

 

From: apnmbx-public--- via Tcl-Core <tcl...@li...
<mailto:tcl...@li...> > 
Sent: Wednesday, June 25, 2025 6:57 AM
To: tcl...@li... <mailto:tcl...@li...> 
Subject: [TCLCORE] TIP #649: Call for Votes

 

This is a CFV for TIP #649: Expose additional list functionality in the C
API

 

Voting period ends 12PM UTC July 5th.

 

/Ashok

Re: [TCLCORE] TIP #649: Call for Votes

[Brian G. <bri...@ea...>]

My vote:

TIP #649:  YES

-Brian

On Jun 24, 2025, at 20:03, apnmbx-public--- via Tcl-Core <tcl...@li...> wrote:

Forgot to include a link to the TIP - https://core.tcl-lang.org/tips/doc/trunk/tip/649.md

From: apnmbx-public--- via Tcl-Core <tcl...@li...>
Sent: Wednesday, June 25, 2025 6:57 AM
To: tcl...@li...
Subject: [TCLCORE] TIP #649: Call for Votes

This is a CFV for TIP #649: Expose additional list functionality in the C API

Voting period ends 12PM UTC July 5th.

/Ashok
_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] TIP #649: Call for Votes

[<apn...@ya...>]

Forgot to include a link to the TIP -
https://core.tcl-lang.org/tips/doc/trunk/tip/649.md

 

From: apnmbx-public--- via Tcl-Core <tcl...@li...> 
Sent: Wednesday, June 25, 2025 6:57 AM
To: tcl...@li...
Subject: [TCLCORE] TIP #649: Call for Votes

 

This is a CFV for TIP #649: Expose additional list functionality in the C
API

 

Voting period ends 12PM UTC July 5th.

 

/Ashok

[TCLCORE] TIP #649: Call for Votes

[<apn...@ya...>]

This is a CFV for TIP #649: Expose additional list functionality in the C
API

 

Voting period ends 12PM UTC July 5th.

 

/Ashok

Re: [TCLCORE] [EXTERNAL] Follow-up: TIP 722: return loaded packages by ”package present”

[Christian W. <Chr...@t-...>]

On 06/24/2025 10:57 PM, Donald G Porter via Tcl-Core wrote:

Thanks for your comments, Don,

> …
> From the description in the message, it looks like the dependency information that
> is reported by the proposed mechanism is...
>
> ... empirical; and
>
> ... consists of package names alone.
>
> So we learn that in the current program run requiring package foo caused the requiring
> of package bar which in turn caused the requiring of packages baz and grok.
>
> Contrast this with the conception of the [package require] command itself.
>
>   package require $pkgName ?$requirement ... $requirement?
>
> which can take the form of
>
>   package require foo 3.1-3.7 4.3
>
> The important point is that a program does not depend on just a package name, but
> on a collection of releases of a package that truly meet the needs of the program.
> If you do not capture the version information as well, you aren't capturing all the
> dependency information on which [package] operates.

Now already here I am at the point where I have to politely doubt the sense of
"package files …". Why did it then make into the "package" command at all, since the
version/minor/micro could be indeed decide on the set of files which make up the
package. And what deeper value is then in this information when the next version's
set is slightly different?
  
> This also illustrates that the conceptual dependency understood by the programmer
> writing the [package require] commands cannot be captured empirically.  The
> program knows that "foo 3.1" or "foo 3.2" or "foo 3.2.4.6" or "foo 3.6.1" or "foo 4.3"
> are all acceptable, but each run of the program can only empirically capture that
> this time "foo 3.4.7" and "foo 3.5.0" were available, and "foo 3.5.0" was provided.

The idea was mainly driven to get a snapshot for the dependencies to make that
snapshot somehow permanent given the means we got by e.g. "zipfs mkimage". Therefore
the tracking of version information of a package is deliberately left out (similar
to "package files …" is version unaware.

> Depending on which version of foo was actually provided, the dependencies that
> get dragged in could well be different.  foo 3.4.7 had a dependency on bar 2. but
> foo 3.5.0 decided to make use of bingo 7 to solve the same problem.
>
> I can see some value in recording a history of how packages came into the interp, but
> the empircal approach does not capture the full dependency tree, realized and
> unrealized, and doesn't result in the sort of data on which you could do a toplogical sort.
> Good for some purposes, but not for the full functionality I would expect to find in
> a [package depends] command.
> …

I see your points and will step back to further bring this idea forward.

All the best,
Christian