• Fixed limitation to 99 sequential plots in plotchart

    From meshparts@[email protected] to comp.lang.tcl on Thu Apr 9 23:25:02 2026
    From Newsgroup: comp.lang.tcl

    Not shure if the the github repo is monitored so here is a note on a bug
    fix that happens when plotting more than 99 sequential plots:

    https://github.com/tcltk/tklib/compare/master...Meshparts:tklib:patch-1
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Arjen@[email protected] to comp.lang.tcl on Fri Apr 10 06:45:27 2026
    From Newsgroup: comp.lang.tcl


    meshparts <[email protected]> posted:

    Not shure if the the github repo is monitored so here is a note on a bug
    fix that happens when plotting more than 99 sequential plots:

    https://github.com/tcltk/tklib/compare/master...Meshparts:tklib:patch-1

    Thanks for pointing this out. I thought that was fixed. But I will have a look!

    Regards,

    Arjen
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Arjen@[email protected] to comp.lang.tcl on Mon Apr 13 18:36:53 2026
    From Newsgroup: comp.lang.tcl


    Arjen <[email protected]d> posted:


    meshparts <[email protected]> posted:

    Not shure if the the github repo is monitored so here is a note on a bug fix that happens when plotting more than 99 sequential plots:

    https://github.com/tcltk/tklib/compare/master...Meshparts:tklib:patch-1

    Thanks for pointing this out. I thought that was fixed. But I will have a look!


    Indeed, it is not yet solved. I found the culprit though that caused the error for XY-plots. I will have to test that my solution works for all plots, but
    my change is in plotpriv.tcl:

    if { [string match {[0-9]*} $w] } {
    set c [string range $w [string first . $w] end]
    } else {
    set c $w
    }

    Originally the second line was:

    set c [string range $w 2 end]

    There are quite a few of these constructs.

    Regards,

    Arjen
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From meshparts@[email protected] to comp.lang.tcl on Tue Apr 14 09:43:58 2026
    From Newsgroup: comp.lang.tcl

    Am 13.04.2026 um 20:36 schrieb Arjen:

    Arjen <[email protected]d> posted:


    meshparts <[email protected]> posted:

    Not shure if the the github repo is monitored so here is a note on a bug >>> fix that happens when plotting more than 99 sequential plots:

    https://github.com/tcltk/tklib/compare/master...Meshparts:tklib:patch-1

    Thanks for pointing this out. I thought that was fixed. But I will have a look!


    Indeed, it is not yet solved. I found the culprit though that caused the error
    for XY-plots. I will have to test that my solution works for all plots, but my change is in plotpriv.tcl:

    if { [string match {[0-9]*} $w] } {
    set c [string range $w [string first . $w] end]
    } else {
    set c $w
    }

    Originally the second line was:

    set c [string range $w 2 end]

    There are quite a few of these constructs.

    Regards,

    Arjen

    I thought, the link I posted shows my changes, but maybe not, because I
    forgot to do a pull request?

    My fix was:

    set c .[join [lrange [split $w .] 1 end] .]

    But your fix is shorter and look better.

    Regards
    Alex
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Arjen@[email protected] to comp.lang.tcl on Tue Apr 14 14:20:03 2026
    From Newsgroup: comp.lang.tcl


    meshparts <[email protected]> posted:



    I thought, the link I posted shows my changes, but maybe not, because I forgot to do a pull request?

    My fix was:

    set c .[join [lrange [split $w .] 1 end] .]

    But your fix is shorter and look better.

    Regards
    Alex

    My apologies - I did not look at the ticket, as I remembered seeing this
    bug before (and thinking it fixed ;)). The corrected code was there in a few places, but not everywhere.

    Regards,

    Arjen
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From meshparts@[email protected] to comp.lang.tcl on Wed Apr 15 10:56:06 2026
    From Newsgroup: comp.lang.tcl

    Am 14.04.2026 um 16:20 schrieb Arjen:
    My apologies - I did not look at the ticket, as I remembered seeing this
    bug before (and thinking it fixed ;)). The corrected code was there in a few places, but not everywhere.
    No worries, not a big deal. Glad it's fixed now.
    --- Synchronet 3.21f-Linux NewsLink 1.2