Open tklib tickets: Reproduced

Triage of all 71 open and Pending tickets of tklib (bugs, patches and feature requests) on 2026-11-15: whether a bug still exists in tklib trunk with Tk 9.1 and 8.6, whether a patch is still needed, and whether a request has been implemented, superseded or become outdated. 25 prototype patches with regression tests; rows marked patch have one. None is committed.

Reproduced 21

🔧79747a0cb52026notifywindow error in successive callspatchREPRODUCED (Tk 9.1, 8.6)

Open ticket 79747a0cb5 · (unused) · Bug · filed 2026-09-10

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-16 check-in e6328aa17c on notifywindow-cancel-timers, not merged: Follow-up to db81761a73 for 79747a0cb5: when a notification replaced one which was still shown, the pending fade_in and fade_out events of the old window st
  • 🔧 2026-09-10 check-in db81761a73 on bug-79747a0cb518, not merged: Fix for bug 79747a0cb5
  • 💬 2026-11-16 serhiy.storchaka: Branch bug-79747a0cb518 destroys the old window, but its pending fade_in and fade_out events still run, so the new notification is faded out and destroyed before its time. Proposed fix on top of it in branch notifywindow-cancel-timers: these events are cancelled.
Full verdict

REPRODUCED (Tk 9.1, 8.6)

  • Module notifywindow · Bug
  • Tested Tk 9.1, 8.6. Two successive notifywindow::notifywindow calls raise window name "_notify" already exists in parent.
  • Cause notifywindow.tcl:notifywindow::notifywindow always creates the fixed toplevel ._notify and never checks whether it already exists. Its pending fade_in/fade_out timers are not tracked, so destroying and recreating the window would let the old 3 s fade_out timer fade the new one early.
  • Prototype 79747a0cb5.patch (+17/−3 in notifywindow.tcl, plus new modules/notifywindow/notifywindow.test; tests notifywindow-1.1 and notifywindow-1.2). A new call replaces a notification that is still shown: pending timer ids are kept in notifywindow::afterids and cancelled, then the old window is destroyed. No version bump.
  • Suggested ticket action Confirmed with Tk 9.1 and 8.6. Fix: a new notification replaces the one still shown, and the old fade timers are cancelled. Stacking several notifications would be a larger change.
🔧fa6fbae0452025widget::dateentry does not accept array as textvariablepatchREPRODUCED (Tk 9.1, 8.6)

Open ticket fa6fbae045 · widget :: dateentry · Bug · filed 2025-02-16

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-16 check-in 329ac63aae on dateentry-textvariable, not merged: Fix fa6fbae045: widget::dateentry did not set its -textvariable, so reading an array element given as -textvariable failed, and an existing value was ignored.
  • 💬 2026-11-16 serhiy.storchaka: Proposed fix in branch dateentry-textvariable. As suggested, the -textvariable is now set when the widget is created: to the date it holds if it is valid, otherwise to the current date. The same happens when -textvariable is configured later. Like for the standard widgets, a variable name which is not fully qualified now refers to a global variable.
Full verdict

REPRODUCED (Tk 9.1, 8.6)

  • Module widget (widget::dateentry) · Bug
  • Tested Tk 9.1.1, 8.6.18. With -textvariable ::A(date) (and also with a scalar), the variable does not exist after the widget is created, so reading it gives "no such element in array". An existing value is ignored. An unqualified name (A(date)) does not work at all: neither setting it nor choosing a date reaches the global variable.
  • Cause dateentry.tcl. The constructor never writes the linked variable. C-textvariable puts the trace on the name from inside the method, and DateChosen uses upvar 0, so an unqualified name resolves in method scope, not globally as for standard widgets.
  • Prototype fa6fbae045.patch (about 31 code lines: new InitTextvariable, called at the end of construction and when -textvariable is changed later. It shows the variable's date if valid, else stores the current date. The trace is set and upvar is done at the global level. New test file modules/widget/dateentry.test, tests dateentry-textvariable-1.1..1.4.)
  • Suggested ticket action Confirmed: the linked variable is never set when the widget is created, and unqualified names are not treated as global. Fix: initialise or adopt the variable at construction and use global scope for the trace and upvar (prototype available), then bump to 0.100 or 1.0. Side finding: the initial date is computed as UTC midnight ([clock seconds]/86400*86400), so just after local midnight east of UTC it shows yesterday.
⬜a033bd45cb2024Bad performance of xyplot packagepatchREPRODUCED (Tk 9.1, 8.6). Fixable.

Open ticket a033bd45cb · plotchart · RFE · filed 2024-08-24

Full verdict

REPRODUCED (Tk 9.1, 8.6). Fixable.

  • Module plotchart (xyplot) · RFE
  • Tested Tk 9.1 and 8.6, 10000 points. xyplot takes about 580 ms and creates 10073 items. A Plotchart plot loop takes about 300 ms, plotlist about 20 ms. Every resize or zoom redraws everything again.
  • Cause plotchart/xyplot.tcl:draw calls $s plot $sid $x $y for every point, creating one canvas line per segment, which is then scaled and moved by rescale.
  • Prototype a033bd45cb.patch (about 15 code lines, plus a new modules/plotchart/xyplot.test, test xyplot-1.1). draw collects x/y lists and draws each series with one plotlist call. 10000 points now take about 60 ms and create 75 items. The data bbox is identical before and after, also after zooming.
  • Suggested ticket action xyplot drew every segment as a separate canvas item. Using plotlist per series makes the initial draw, resize and zoom about 10 times faster. A fix is available.
🔧e9c4eeae1f2024diagrams not rendered properpatchREPRODUCED (Tk 9.1, 8.6; tcllib math::geometry 1.4.2). The attached diagrams.diff (blob 2a6805ba01…) is missing from the local repository and could…

Open ticket e9c4eeae1f · diagrams · Bug · filed 2024-07-23

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-15 check-in aea758e6eb on diagrams-screen-directions, not merged: Fix e9c4eeae1f and ffcd8611b8: line north goes down in diagrams. Since math::geometry 1.4 (tcllib check-in 1f54de21e6) [direction] and [octant] use the math
  • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch diagrams-screen-directions. Since math::geometry 1.4 (tcllib check-in 1f54de21e6) direction and octant use the mathematical orientation of the y axis, but the y axis of the canvas points down. diagrams now has its own versions of both, which behave like math::geometry before 1.4.
Full verdict

REPRODUCED (Tk 9.1, 8.6; tcllib math::geometry 1.4.2). The attached diagrams.diff (blob 2a6805ba01…) is missing from the local repository and could not be reviewed.

  • Module diagrams · Bug
  • Tested line north goes down on the screen. line from [0 0] then [by 10 90] ends at y=+10. The circle northeast corner is at (7, 7), i.e. below the centre. The 4e6715533c script gets broken arrows.
  • Cause tcllib check-in 1f54de21e6 (2020-09-20, math::geometry 1.4.0) switched math::geometry::direction and octant to the mathematical y orientation. diagrams uses them in screen coordinates (y down) in point.tcl polar2cartesian and in basic.tcl (circle corners, LineCorners, arc direction). It requires only math::geometry 1.1.2, so it silently picks up the incompatible change.
  • Prototype e9c4eeae1f.patch (about 29 code lines plus a new modules/diagrams/diagrams.test; tests diagram-direction-1.1 to 1.3). It defines screen-oriented direction and octant in ::diagram::point::geo, which override the imported ones, and imports them into ::diagram::basic::geo. This makes diagrams independent of the math::geometry version. All 63 figures still render.
  • Suggested ticket action Since math::geometry 1.4 (tcllib 1f54de21e6), direction/octant use the mathematical y axis, while diagrams works in canvas coordinates. Fixed by giving diagrams its own screen-oriented versions. Close as Fixed after commit; also close ffcd8611b8.
🔧ffcd8611b82021direction and octant delete the minus sign lead to diagram display bugsREPRODUCED (Tk 9.1, 8.6). Duplicate of e9c4eeae1f, same cause: tcllib 1f54de21e6, 2020-09-20. The tcllib side was an intentional fix for tcllib t…

Open ticket ffcd8611b8 · diagrams · Bug · filed 2021-06-16

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-15 check-in aea758e6eb on diagrams-screen-directions, not merged: Fix e9c4eeae1f and ffcd8611b8: line north goes down in diagrams. Since math::geometry 1.4 (tcllib check-in 1f54de21e6) [direction] and [octant] use the math
  • 💬 2026-11-15 serhiy.storchaka: This is the same issue as e9c4eeae1f. Proposed fix in branch diagrams-screen-directions.
Full verdict

REPRODUCED (Tk 9.1, 8.6). Duplicate of e9c4eeae1f, same cause: tcllib 1f54de21e6, 2020-09-20. The tcllib side was an intentional fix for tcllib ticket fb4812f82b, so diagrams has to adapt.

🔧b845a924db2020Tachometer : a wrong angle is calculated in method drawlinepatchREPRODUCED (Tk 9.1, 8.6). Also found: with Tk 9, controlwidget::tachometer .t with the default size fails with `cannot use non-numeric string "50…

Open ticket b845a924db · controlwidget · Bug · filed 2020-09-20

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-15 check-in 415c80d49d on tachometer-needle-angle, not merged: Fix b845a924db: the tachometer needle angle was computed with integer division when -min, -max and the value are integers. Also, with Tk 9 the tachometer fail
  • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch tachometer-needle-angle. The angle is now computed in floating point. The branch also fixes another problem: with Tk 9 the tachometer failed with its default size, because cget -width of the canvas returns "50m" instead of pixels.
Full verdict

REPRODUCED (Tk 9.1, 8.6). Also found: with Tk 9, controlwidget::tachometer .t with the default size fails with cannot use non-numeric string "50m". Tk 9 returns the canvas -width as given ("50m") rather than in pixels.

  • Module controlwidget (tachometer 0.2) · Bug
  • Tested Tk 9.1, 8.6. With -min 0 -max 10 and value 1 the needle is drawn as for value 0, and the coordinates differ from -max 10.0.
  • Cause tachometer.tcl:drawline computes ($v-$min)/($max-$min) with integer division when all three are integers. The constructor and drawline use [$c cget -width] directly in expr, which breaks with screen distances such as 50m in Tk 9.
  • Prototype b845a924db.patch (+4/−4 in tachometer.tcl: double($value) and winfo pixels for width/height, plus new modules/controlwidget/controlwidget.test; tests tachometer-1.0, 1.1 and 1.2). No version bump. This patch and 7ae7ab1e83 both create controlwidget.test, so they must be merged by hand if both are applied.
  • Suggested ticket action Confirmed. Integer arithmetic truncates the needle angle. Fixed by forcing floating point. The prototype also fixes the Tk 9 failure with the default "50m" size.
🔧e7f1ed859e2020The ICO package does not handle 256x256 icons properlypatchREPRODUCED (Tk 9.1, 8.6). iconMembers of a 256x256 icon returns {0 0 0 32}. In a file with 16 and 256 icons, getIcon -res 256 cannot match th…

Open ticket e7f1ed859e · ico · Bug · filed 2020-09-12

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-15 check-in 7425d4463d on ico-256-icons, not merged: Fix e7f1ed859e: ico read 256x256 icons as size 0. In the icon directory a width or height of 0 means 256. getIconMembersICODATA also read sizes from 128 to 25
  • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch ico-256-icons. As suggested, a width or height of 0 in the icon directory is now read as 256. In addition, the reader for icon data no longer returns negative sizes for icons from 128 to 255 pixels.
Full verdict

REPRODUCED (Tk 9.1, 8.6). iconMembers of a 256x256 icon returns {0 0 0 32}. In a file with 16 and 256 icons, getIcon -res 256 cannot match the large one. The ICODATA member reader (binary scan ccc) also returns negative sizes for 128 to 255.

  • Module ico · Bug
  • Tested wrote 16/200/256 icons into one ICO file, then checked iconMembers, getIconMembersICODATA and getIcon -res.
  • Cause ico.tcl getIconMembersICO and getIconMembersICODATA take the directory width/height byte literally (0 means 256) and, for ICODATA, as signed.
  • Prototype e7f1ed859e.patch (about 13 code lines plus a new modules/ico/ico.test; test ico-members-1.1). It maps 0 to 256 in both readers and masks the ICODATA bytes with & 0xFF, keeping Tcl 8.4 syntax as ico requires.
  • Suggested ticket action Confirmed. A size byte of 0 in the icon directory means 256. Fixed in getIconMembersICO and getIconMembersICODATA, essentially as suggested (the ICODATA bytes are now also read unsigned). Close as Fixed after commit.
🔧7ae7ab1e832019rdial "can't read 'sfact'" with tkinter errorpatchREPRODUCED (Tk 9.1, 8.6). Nothing tkinter-specific: controlwidget::rdial .r fails whenever -width is not given explicitly.

Open ticket 7ae7ab1e83 · controlwidget · Bug · filed 2019-07-19

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-15 check-in bb38f4cff1 on rdial-default-width, not merged: Fix 7ae7ab1e83: controlwidget::rdial failed with the default -width (can't read "sfact"). The scale factor was only computed when -width was given; compute it
  • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch rdial-default-width. Nothing specific to tkinter: rdial failed whenever -width was not given, because the scale factor was only computed when the option was set. It is now also computed in the constructor.
Full verdict

REPRODUCED (Tk 9.1, 8.6). Nothing tkinter-specific: controlwidget::rdial .r fails whenever -width is not given explicitly.

  • Module controlwidget (rdial 0.7) · Bug
  • Tested Tk 9.1, 8.6: controlwidget::rdial .r → Error in constructor: can't read "sfact": no such variable.
  • Cause rdial.tcl: sfact is computed only in SetOption for -width, which runs only when -width is passed. With the default width, draw uses an unset sfact.
  • Prototype 7ae7ab1e83.patch (1 line in the constructor: set sfact [expr {$ssize*2/$options(-width)}], plus new modules/controlwidget/controlwidget.test; tests rdial-1.0 and rdial-1.1). No version bump.
  • Suggested ticket action Confirmed: rdial fails with the default -width. Fix: compute the scale factor in the constructor (prototype attached).
⬜d74509223b2018widget::listentry and widget::listsimple package require 'img::png' but should require pngpatchREPRODUCED (Tk 9.1, 8.6): package require widget::listentry / widget::listsimple fails with "can't find package img::png" when the Img extensio…

Open ticket d74509223b · widget · Bug · filed 2018-01-23

Full verdict

REPRODUCED (Tk 9.1, 8.6): package require widget::listentry / widget::listsimple fails with "can't find package img::png" when the Img extension is not installed.

  • Module widgetl · Bug
  • Tested Tk 9.1.1, 8.6.18
  • Cause listentry.tcl and listsimple.tcl call package require img::png unconditionally. Tk 8.6+ reads PNG natively. The ticket's suggested package require png is the tcllib metadata package and has nothing to do with this; it only "works" because Tk 8.6 already reads PNG.
  • Prototype d74509223b.patch (8 code lines: require img::png only on Tk < 8.6; new test file modules/widgetl/widgetl.test, tests widgetl-load-1.1..1.2)
  • Suggested ticket action Confirmed. Tk 8.6+ reads PNG natively, so require img::png only for Tk 8.5, and bump both packages to 0.1.3 (prototype available). Do not use the suggested package require png; it is unrelated. Side finding: widget::validator (module widgetv) keeps references to destroyed entries. Destroying a listsimple and then creating another listsimple/listentry gives an "invalid command name .x.e" background error from StylePropagation, and attaching to a reused path name fails with "Unable to attach, .l.e already in use".
🔧6da48f45792016autoscroll assumes packed widget managed by parentpatchREPRODUCED (Tk 9.1, 8.6)

Open ticket 6da48f4579 · autoscroll · Bug · filed 2016-04-05

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-16 check-in ad0d5c7779 on autoscroll-pack-in, not merged: Fix 6da48f4579: autoscroll assumed that a packed scrollbar is managed in its parent. With pack -in another container it saved and restored the wrong pack orde
  • 💬 2026-11-16 serhiy.storchaka: Proposed fix in branch autoscroll-pack-in. The container is now taken from pack info.
Full verdict

REPRODUCED (Tk 9.1, 8.6)

  • Module autoscroll · Bug
  • Tested Tk 9.1, 8.6. A scrollbar packed with -in .f (master is not its parent) is hidden once the content fits, and is then never packed again when scrolling is needed (pack info .s → "isn't packed").
  • Cause autoscroll.tcl:widgetCommand saves the pack info of [pack slaves [winfo parent $w]]. That list does not contain $w when it is packed in another master, so the scrollbar is not restored.
  • Prototype 6da48f4579.patch (1-line fix as suggested in the ticket: [pack slaves [lindex [pack info $w] 1]], which keeps the package's old Tcl baseline). Adds new modules/autoscroll/autoscroll.test with tests autoscroll-1.0 (grid), autoscroll-1.1 (pack) and autoscroll-1.2 (pack -in, the regression test).
  • Suggested ticket action Confirmed. The suggested fix is correct and is in the attached prototype with tests. Apply it and bump autoscroll to 1.1.1.
🔧4c5222924f2015ipentry::ipentry crash after window is destroyed and recreatedpatchREPRODUCED (Tk 9.1, 8.6): "bad operation list "": must be one or more of array, read, unset, or write".

Open ticket 4c5222924f · ipentry · Bug · filed 2015-01-23

🔧 Since triage (updated 2026-11-16)

Status now: Open

  • 🔧 2026-11-16 check-in 38862c9602 on ipentry-remove-traces, not merged: Fix 4c5222924f: ipentry failed after it was destroyed and created again with the same -textvariable. Destroying it removed the first trace of the variable, wh
  • 💬 2026-11-16 serhiy.storchaka: Proposed fix in branch ipentry-remove-traces. When the widget was destroyed, it removed the first trace of its -textvariable, whichever it was, and could leave its own trace, which then failed for the new widget. Now it removes exactly its own trace.
Full verdict

REPRODUCED (Tk 9.1, 8.6): "bad operation list "": must be one or more of array, read, unset, or write".

  • Module ipentry · Bug
  • Tested ticket script; also two ipentries sharing one variable, then destroying the first.
  • Cause ipentry.tcl destroyWidget removes whichever trace comes first on the variable, which can be another widget's or the user's trace. It also never unsets ::ipentry::textvars($w). When the widget is recreated, configure -textvariable sees the stale entry and calls trace remove with an empty trace spec. It also looked up the trace on the new variable instead of the old one. The trace re-added in the unset branch used ipentry::traceFired without the leading ::.
  • Prototype 4c5222924f.patch (about 25 code lines plus a new modules/ipentry/ipentry.test; tests ipentry-textvariable-2.1, ipentry-textvariable-2.2). It adds ::ipentry::untraceVar, which removes exactly this widget's trace and forgets the variable. It is used by destroyWidget and configure -textvariable, and the trace command prefix is now consistent.
  • Suggested ticket action Fixed: the widget now removes exactly its own trace on destroy or reconfigure and forgets the variable, so the widget can be recreated and other traces on the variable are kept. Close as Fixed after commit.
⏳50309a59362014Cumulatively plotting in a histogram does not work properly - overlaid barsREPRODUCED (Tk 9.1, 8.6)

Open ticket 50309a5936 · plotchart · Bug · filed 2014-12-11

⏳ Since triage (updated 2026-11-16)

Status now: Pending

    Full verdict

    REPRODUCED (Tk 9.1, 8.6)

    • Module plotchart · Bug
    • Tested Tk 9.1 and 8.6, the ticket script. The second red bar of data2 goes from 0 to 3 (1+2) and completely covers the green bar of data.
    • Cause plotpriv.tcl:DrawHistogramCumulative only keeps a running sum within the same series (data_series($w,$series,y)) and draws via DrawHistogramData from ymin. It never stacks on top of other series at the same x.
    • Prototype none (the intended semantics are undecided. The maintainer said in 2024 he will "correct or remove" the method). One possible fix: keep a per-x base scaling($w,histbase,$x) that every plot/plotcumulative updates, and draw the cumulative bar from that base to base+y. That changes the meaning of the method.
    • Suggested ticket action Still present: plotcumulative accumulates within one series (a running sum) instead of stacking on the other series. Decide which semantics are intended (see a6dd880cf2), then fix or deprecate the method.
    ⬜ee430592d92014Barchart data are drawn outside the area if the axis does not start at zeropatchREPRODUCED (Tk 9.1, 8.6)

    Open ticket ee430592d9 · plotchart · Bug · filed 2014-12-11

    Full verdict

    REPRODUCED (Tk 9.1, 8.6)

    • Module plotchart · Bug
    • Tested Tk 9.1 and 8.6, the attached barchart_test.tcl (y axis 6..35), plus vertical and horizontal bar charts with axis {6 36 6}: 3 bar corners fall below/left of the plot area in each.
    • Cause plotpriv.tcl:DrawVertBarData / DrawHorizBarData draw each bar from the base (initially 0.0, see plotaxis.tcl:DrawXlabels/DrawYlabels) to base+value without regard to the axis range.
    • Prototype ee430592d9.patch (about 35 code lines + test, test Plotchart-6.4). New helper ClipToRange clamps both bar ends to [ymin,ymax] (or [xmin,xmax] for horizontal bars). Stacking and showvalues are unchanged, and bars drawn from the origin when the axis contains it are unchanged. The attached script runs fine.
    • Suggested ticket action Confirmed. Clamping the bar ends to the axis range keeps the bars inside the plot area. A fix is available. (The margin issue mentioned in the ticket is not covered.)
    ⬜6812273b4d2014Plotchart "bindplot" not sensitive when cursor is over data/linespatchREPRODUCED (Tk 9.1, 8.6)

    Open ticket 6812273b4d · plotchart · Bug · filed 2014-09-05

    Full verdict

    REPRODUCED (Tk 9.1, 8.6)

    • Module plotchart · Bug
    • Tested Tk 9.1 and 8.6, xyplot with a line and symbols plus bindplot <ButtonPress-1>. A click on the data point (5,5) does not call the callback. A click on empty space (2,7) does.
    • Cause plotbind.tcl:BindPlot binds the event to an invisible rectangle and then lowers it below everything ($w lower $scaling($w,eventobj)), so any data, background or gradient item on top receives the event. Raising it instead would shadow bindlast, the legend and balloons.
    • Prototype 6812273b4d.patch (about 50 code lines + test, test Plotchart-6.3). BindPlot now adds (+) a widget-level binding on the real canvas, once per plot/event, which calls a new BindPlotCmd. BindPlotCmd checks that the point (canvasx/canvasy) is inside the plot area and calls the stored command, so a later bindplot for the same event replaces it. Item bindings (bindlast, legend drag) keep working. Behaviour change: <Enter>/<Leave> now refer to the canvas window, not the plot rectangle.
    • Side finding DrawGradientBackground (plotannot.tcl) no longer draws vertical gradients (top-down/bottom-up) because nmax is negative ($rymin-$rymax), as noted in the 2024 comment. Also methodProc(xyplot,bindcmd) points to BindCmd with an incompatible signature (the canvas-wide BindCmd is inside if {0}). Both are worth separate tickets.
    • Suggested ticket action Confirmed: the event rectangle is lowered below all items, so events over data or background never reach it. A fix that binds to the canvas and filters on the plot area is available. The vertical gradient background is a separate bug (negative nmax).
    🔧3567463fff2012ctext sends <<Modified>> too oftenpatchREPRODUCED (Tk 9.1, 8.6)

    Open ticket 3567463fff · ctext · Bug · filed 2012-09-13

    🔧 Since triage (updated 2026-11-16)

    Status now: Open

    • 🔧 2026-11-15 check-in 8b53c6beb2 on ctext-modified-event, not merged: Fix 3567463fff: ctext sent <<Modified>> on every change, and not at all for "edit modified". Like the text widget, <<Modified>> is now sent only when the modi
    • 🔧 2026-11-15 check-in adab3e651c on ctext-modified-event, not merged: ctext: let the text widget keep the modified flag. ctext is in the bindtags of its text widget, so the <<Modified>> the text widget sends also reached bindings
    • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch ctext-modified-event. ctext is in the bindtags of its text widget, so bindings on the ctext received the > of the text widget in addition to the one ctext sent itself after every change. Now the text widget keeps the modified flag, as in a plain text widget: > is sent once each time the flag changes, also when it is set with edit modified.
    Full verdict

    REPRODUCED (Tk 9.1, 8.6)

    • Module ctext · Bug
    • Tested bind <<Modified>> on a ctext. 3 inserts give 3 events (a text widget gives 1). .t edit modified 0 gives no event at all, although the flag changes.
    • Cause ctext.tcl ctext::modified always runs event generate $win <<Modified>>. The edit modified <value> branch of ctext::instanceCmd sets ar(modified) directly, so it never sends an event.
    • Prototype 3567463fff.patch (9 code lines plus a new modules/ctext/ctext.test; tests ctext-modified-1.1, ctext-modified-1.2). It sends the event only when the normalised flag changes, and edit modified now goes through ctext::modified.
    • Suggested ticket action Fixed by sending <<Modified>> only when the modified flag actually changes, like the text widget. $w edit modified 0/1 now also sends the event. Close as Fixed after commit.
    🔧3470437fff2012Padding on and mask rasters incorrect.patchREPRODUCED (Tk 9.1, 8.6). Writing an icon with transparent pixels and reading it back gives a corrupted mask for widths 8, 20 and 40. Widths 16, 24…

    Open ticket 3470437fff · ico · Bug · filed 2012-01-06

    🔧 Since triage (updated 2026-11-16)

    Status now: Open

    • 🔧 2026-11-15 check-in d227043609 on ico-andmask-padding, not merged: Fix 3470437fff: wrong padding of the AND mask rows in ico. Each row of the mask is padded to a multiple of 32 bits, but ico padded it with (width % 32) bits,
    • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch ico-andmask-padding. The rows of the AND mask are now padded to a multiple of 32 bits as suggested, both when writing and when reading, in ico 1.x and in the old ico 0.x. The sizes which worked before (16, 24, 32, 48, 64, 256) are not affected, except 24 in ico 0.x, which was wrong too.
    Full verdict

    REPRODUCED (Tk 9.1, 8.6). Writing an icon with transparent pixels and reading it back gives a corrupted mask for widths 8, 20 and 40. Widths 16, 24, 32, 48, 64 and 256 pad correctly only by coincidence.

    • Module ico · Bug
    • Tested writeIcon 24 bpp with transparent pixels, then getIcon -format colors, for widths 8/16/20/24/40/48, via ICO files and the ICODATA reader.
    • Cause ico.tcl getAndMaskFromColors pads each row with w % 32 zero bits (special case 8 for 24) instead of (32 - w % 32) % 32. The readers have the same wrong row size: readDIB and readDIBFromData, and the corresponding lines in ico0.tcl.
    • Prototype 3470437fff.patch (6 code lines in ico.tcl and ico0.tcl plus a new modules/ico/ico.test; tests ico-andmask-1.<size>, ico-andmask-2.<size>). It uses the formula from the ticket for writing and ((w+31)/32)*4*h bytes for reading. Results for the standard sizes are unchanged.
    • Side finding getIcon and getIconByName with -type ICODATA always fail with "couldn't open …", because they run file exists on the data. writeIconICODATA is broken too (@{$readpos}).
    • Suggested ticket action Confirmed. The AND mask rows were padded to a wrong length, both when writing and when reading, for widths that are not 16, 24, 32, 48 or a multiple of 32. Fixed in writer and reader. Close as Fixed after commit.
    🔧2962077fff2010error if an array element is used as -textvariablepatchREPRODUCED (Tk 9.1, 8.6): set foo(bar) 1.1.1.2 raises "can't read "var": variable is array". The attached patch's code hunks still apply (with an…

    Open ticket 2962077fff · ipentry · Bug · filed 2010-03-02

    🔧 Since triage (updated 2026-11-16)

    Status now: Open

    • 🔧 2026-11-16 check-in f1d6e65970 on ipentry-array-textvariable, not merged: Fix 2962077fff: ipentry and ipentry6 failed with an array element as -textvariable. The trace procedures used the name and key passed by the trace, which are
    • 💬 2026-11-16 serhiy.storchaka: Proposed fix in branch ipentry-array-textvariable. The trace procedures used the variable name passed to the trace, which for an array element does not include the element. They now use the name the widget was configured with. This fixes ipentry6 too.
    Full verdict

    REPRODUCED (Tk 9.1, 8.6): set foo(bar) 1.1.1.2 raises "can't read "var": variable is array". The attached patch's code hunks still apply (with an offset). Its version-bump hunks are obsolete (ipentry is 0.3.2 now).

    • Module ipentry · Bug
    • Tested ticket script with ipentry and ipentry6.
    • Cause ipentry.tcl traceFired/traceFired6 run upvar #0 $name var on the trace's name1 and ignore name2. The attached patch adds ($key), but name1 is still relative to the frame that accessed the variable.
    • Prototype 2962077fff.patch (4 code lines plus a new modules/ipentry/ipentry.test; tests ipentry-textvariable-1.1, ipentry-textvariable-1.2). The trace callbacks take the variable name from ::ipentry::textvars($w) instead of the trace arguments. This is more robust than the attachment.
    • Suggested ticket action Fixed by using the stored textvariable name in the trace callbacks instead of the name passed by the trace, which is relative to the accessing frame. Close as Fixed after commit.
    ⬜2683544fff2009clipped x-labels due to font sizepatchREPRODUCED (Tk 9.1, 8.6), partially. The clipping was fixed in 08fd0b98c8 2009-05-10 ("Solved issue 2683544"), but the follow-up report still hol…

    Open ticket 2683544fff · plotchart · Bug · filed 2009-03-11

    Full verdict

    REPRODUCED (Tk 9.1, 8.6), partially. The clipping was fixed in 08fd0b98c8 2009-05-10 ("Solved issue 2683544"), but the follow-up report still holds: the x-axis text overlaps the tick labels, and at large fonts slightly exceeds the canvas.

    • Module plotchart · Bug
    • Tested Tk 9.1 and 8.6. With font configure TkDefaultFont -size 11 -weight bold the tick labels span y 254..283 and the xtext 282..304 in a 302 px canvas. With a 30 px bottomaxis font the overlap is about 20 px.
    • Cause plotaxis.tcl:DrawXtext places the text at pymax + config($w,font,char_height) + 4. That value is the default-font height cached when the package loaded, not the bottomaxis font, and the tick length and label offset are ignored. plotpriv.tcl:MarginsRectangle reserves 2*char_height+2 using the canvas default font, again ignoring the axis font and the tick offset.
    • Prototype 2683544fff.patch (about 15 code lines + test, test Plotchart-6.5). DrawXtext puts the text at pymax + tick offset + linespace of the bottomaxis font. MarginsRectangle reserves max(char_height, linespace)*2 + offtick. The full plotchart suite still passes on 9.1 and 8.6.
    • Suggested ticket action Clipping was fixed in 08fd0b98c8, but the x-axis title still overlaps the tick labels when the axis font is larger than the default font, because its position uses a font height cached when the package loads. A fix that uses the bottomaxis font metrics and the tick offset is available.
    ⬜2346118fff2008canvas::sqmap limitationsREPRODUCED (Tk 9.1, 8.6)

    Open ticket 2346118fff · tklib · Bug · filed 2008-11-25

    Full verdict

    REPRODUCED (Tk 9.1, 8.6)

    • Module canvas (canvas::sqmap) · Bug
    • Tested Tk 9.1.1, 8.6.18. Made an sqmap with one image cell and one user rectangle. find all / find overlapping return the internal image item too, and gettags on it shows canvas::sqmap::cells.
    • Cause canvas_sqmap.tcl delegates every canvas method except lower/raise/scan/xview/yview straight to the hull. The source comment ("The last 5% needing 90% of the effort. * Defered *") says this was left on purpose.
    • Prototype none (doing it properly means wrapping every item and tag method: find, gettags, addtag, dtag, delete all, itemconfigure all, bbox, select, …. That is an API-wide change.)
    • Suggested ticket action Still true in trunk: internal cell items show up in find/gettags and can be hit by delete all. This is a known design limitation, documented in the source. Keep open as an RFE, or close as "Won't Fix" and document the limitation in canvas_sqmap.man.
    ⬜1346295fff2005plotchart files in release have wrong unix permissionsREPRODUCED (repository state). In the trunk baseline manifest 23 files under modules/plotchart still have the x bit: NEWS, pkgIndex.tcl, plotchart.…

    Open ticket 1346295fff · plotchart · Bug · filed 2005-11-02

    Full verdict

    REPRODUCED (repository state). In the trunk baseline manifest 23 files under modules/plotchart still have the x bit: NEWS, pkgIndex.tcl, plotchart.man, the *.test files and most *.tcl files. Fossil tarballs keep it. Other modules have the same problem: controlwidget (6), ctext (6), khim (5), datefield (2), diagrams ChangeLog and pkgIndex.tcl, notifywindow/pkgIndex.tcl, swaplist/swaplist.tcl.

    • Module plotchart · Bug
    • Tested fossil artifact of the trunk baseline manifest (F-cards with "x").
    • Cause files were committed with an executable mode.
    • Prototype none (a mode change: chmod -x the files, then fossil commit; a diff cannot express it). Keep x only on real scripts such as modules/diagrams/tools/make_figures and show_figures.
    • Suggested ticket action Still true in trunk. Clear the executable bit on all non-script files under modules/ (plotchart and the others listed) and commit. Then close as Fixed.
    🔧1167772fff2005code/block expansionpatchREPRODUCED (Tk 9.1, 8.6). The bug reported in the mail still exists. The mail's code (24 KB) was never attached, so there is no patch to apply.

    Open ticket 1167772fff · tklib: ctext · Patch · filed 2005-03-21

    🔧 Since triage (updated 2026-11-16)

    Status now: Open

    • 🔧 2026-11-15 check-in d2c98b5d41 on ctext-keep-user-tags, not merged: Fix 1167772fff: ctext removed the user's tags around every insert and delete. Only the tags of the highlight classes are removed now. Since edits no longer re
    • 💬 2026-11-15 serhiy.storchaka: Proposed fix in branch ctext-keep-user-tags. On every insert and delete ctext removed all tags except its comment tag from the edited lines, including the user's own tags. Now it only removes the tags of the highlight classes, which are added back when the lines are highlighted again.
    Full verdict

    REPRODUCED (Tk 9.1, 8.6). The bug reported in the mail still exists. The mail's code (24 KB) was never attached, so there is no patch to apply.

    • Module ctext · Patch
    • Tested Tk 9.1.1, 8.6.18. Inserted "hello world" with tag mytag, then insert 1.5 X or delete 1.5: all mytag ranges are removed.
    • Cause ctext.tcl instanceCmd insert/delete removes every tag except _cComment in the affected range, so user tags are lost. The "code expansion" part is only the example in the mail, not a feature request.
    • Prototype 1167772fff.patch (about 21 code lines: the new ctext::removeHighlightTags removes only highlight-class tags; deleteHighlightClass/clearHighlightClasses now delete their tags; new modules/ctext/ctext.test, tests ctext-usertags-1.1..1.4). NOTE: the batch-01 prototype 3567463fff also creates modules/ctext/ctext.test, so merge the two files.
    • Suggested ticket action ctext still strips all user tags (except _cComment) around every insert/delete, so it cannot be used with application tags. Fix: remove only the tags of the highlight classes (prototype available). The original code from the mail was never attached.

    Patch still applies 6

    ⬜8bbf1faad02017Typo fix for license text in several tklib filespatchPATCH-APPLIES. All four files still have "(GPL) ir the Tcl BSD derived license".

    Open ticket 8bbf1faad0 · controlwidget · Patch · filed 2017-07-12

    Full verdict

    PATCH-APPLIES. All four files still have "(GPL) ir the Tcl BSD derived license".

    • Module controlwidget · Patch
    • Tested applied to trunk.
    • Cause typo in header comments.
    • Prototype 8bbf1faad0.patch (4 lines, the submitted patch). No test: the change is to comments only.
    • Suggested ticket action Trivial and correct, apply and close as Fixed.
    ⬜2a98e111892017Russian abbreviated names of days of the week in the calendar widgetpatchPATCH-APPLIES (trunk still has the lowercase three-letter forms "вос пон вто …"; the standard abbreviations are "Вс Пн Вт Ср Чт Пт Сб")

    Open ticket 2a98e11189 · widget · Patch · filed 2017-01-20

    Full verdict

    PATCH-APPLIES (trunk still has the lowercase three-letter forms "вос пон вто …"; the standard abbreviations are "Вс Пн Вт Ср Чт Пт Сб")

    • Module widget (widget::calendar) · Patch
    • Tested Tk 9.1.1, 8.6.18. Checked the weekday header items of widget::calendar -language ru.
    • Cause calendar.tcl LANGS(weekdays,ru)
    • Prototype 2a98e11189.patch (2 code lines, same as the ticket's patch; new test file modules/widget/calendar.test, test calendar-language-1.1)
    • Suggested ticket action Correct, and still needed. Apply it (prototype with test available) and bump widget::calendar to 1.0.3. Side finding: the weekdays,gr and weekdays,he entries in calendar.tcl are mojibake (double-encoded UTF-8 with "?"), so they need a separate fix.
    ⬜42622db1982015Patch to the swaplist default <Double-Button-1> binding that causes an error with -embed optionpatchPATCH-APPLIES (bug REPRODUCED (Tk 9.1, 8.6): double-click in an embedded swaplist raises invalid command name ".t.lr.right"/".t.lr.left", and n…

    Open ticket 42622db198 · swaplist · Patch · filed 2015-09-10

    Full verdict

    PATCH-APPLIES (bug REPRODUCED (Tk 9.1, 8.6): double-click in an embedded swaplist raises invalid command name ".t.lr.right"/".t.lr.left", and nothing moves)

    • Module swaplist · Patch
    • Tested Tk 9.1 and 8.6, swaplist with -embed directly in a toplevel and inside a frame. Synthesized double clicks on both listboxes.
    • Cause swaplist.tcl:Double derives the widget from [winfo toplevel $w], which is only correct for the dialog form. The attachment itself (swaplist.tcl.patch) is not in the repository (SF migration), but the full diff is in the ticket description.
    • Prototype 42622db198.patch (about 10 code lines, the ticket's change, plus a new modules/swaplist/swaplist.test with tests swaplist-1.1 and swaplist-1.2. The tests install an interp bgerror handler so a regression doesn't hang on the error dialog). Remaining issue: with -embed the <Key-Up>/<Key-Down> bindings on $w (a frame) never fire, because the frame is not in the listboxes' bindtags.
    • Suggested ticket action Confirmed. Passing the swaplist path and side to Double, as the ticket proposes, fixes double-click for embedded swaplists. Apply with the new test and close as Fixed.
    ⬜4c28633e3a2015Missing arg for ::Plotchart::DrawLogYaxis in plotaxis.tclpatchPATCH-APPLIES (bug REPRODUCED (Tk 9.1, 8.6): yconfig on xlogyplot/logxlogyplot whose y axis was given without a step, e.g. {1 1000}, fails with…

    Open ticket 4c28633e3a · plotchart · Patch · filed 2015-03-18

    Full verdict

    PATCH-APPLIES (bug REPRODUCED (Tk 9.1, 8.6): yconfig on xlogyplot/logxlogyplot whose y axis was given without a step, e.g. {1 1000}, fails with wrong # args: should be "DrawLogYaxis w ymin ymax ydelt")

    • Module plotchart · Patch
    • Tested Tk 9.1 and 8.6, createXLogYPlot and createLogXLogYPlot with y scale {1 1000}, then yconfig -format %.2f. With a 3-element scale it works, which is why plotdemos11 is needed to trigger it.
    • Cause plotaxis.tcl:AxisConfig calls $drawmethod $w $ymin $ymax {} -ylabels $ydelt when ydelt is not a single number, but DrawLogYaxis has no args (unlike DrawLogXaxis).
    • Prototype 4c28633e3a.patch (2 code lines + test, test Plotchart-6.2). This is the ticket's proposal: add args (ignored) to DrawLogYaxis.
    • Suggested ticket action Confirmed with a log-Y axis specified without a step. Adding args to DrawLogYaxis, as already done for DrawLogXaxis, fixes it. Apply and close as Fixed.
    ⬜38d95aee722015Syntax error prevents xconfig to work for log plots ( plotchart )patchPATCH-APPLIES (bug REPRODUCED (Tk 9.1, 8.6): $p xconfig ... on an X-logY plot gives invalid command name "XConfigXlogY")

    Open ticket 38d95aee72 · plotchart · Patch · filed 2015-03-15

    Full verdict

    PATCH-APPLIES (bug REPRODUCED (Tk 9.1, 8.6): $p xconfig ... on an X-logY plot gives invalid command name "XConfigXlogY")

    • Module plotchart · Patch
    • Tested Tk 9.1 and 8.6, createXLogYPlot + xconfig -format %.2f
    • Cause plotchart.tcl:122 set methodProc(xlogyplot,xconfig) XConfigXlogY (the proc is XConfigXLogY in plotaxis.tcl)
    • Prototype 38d95aee72.patch (1 code line + test, test Plotchart-6.1). This is the ticket's proposed change.
    • Suggested ticket action Confirmed: the method table refers to XConfigXlogY, but the proc is XConfigXLogY. Apply the one-character fix (with a test) and close as Fixed.
    ⬜2829049fff2009"failure" or missing feature in "getstring"patchPATCH-APPLIES (the code is unchanged since 2005; the attached patch still applies)

    Open ticket 2829049fff · tklib · Bug · filed 2009-07-29

    Full verdict

    PATCH-APPLIES (the code is unchanged since 2005; the attached patch still applies)

    • Module getstring · Bug (patch attached)
    • Tested Tk 9.1.1, 8.6.18. Without the change, an existing value in the variable is ignored: the entry starts empty and the value is overwritten.
    • Cause tk_getString.tcl never reads the variable before building the dialog. Also, wm withdraw comes after the widgets are built; this is harmless, as the 2009 comment says. The attached patch alone leaves OK disabled when the initial value is non-empty (with -allowempty 0).
    • Prototype 2829049fff.patch (about 9 code lines: the attached patch, plus enabling OK for a prefilled value and a man page sentence; new test file modules/getstring/getstring.test, tests getstring-initial-1.1..1.3)
    • Suggested ticket action The patch still applies. Prefilling the entry from the variable is a useful feature. Apply it, together with enabling the OK button when the prefilled value is not empty, and document it in tk_getString.man (prototype available).