Skip to main content

Simplifying the use of the Progress Bar.

The basic implementation of the progressBar widget allows the setting of the "fraction" property of the GtkProgressBar but using this options requires more on the Tcl-side than it needs to.

Combination of the new options -range and -steps along with the new sub-commands step, incr and reset help to simplify matters.

For simple lists use the step subcommand along with the the -steps option to indicate the progress of a small, known number of steps where feedback on the completion of each step is required. Setting the -steps option to 10, for example, will set the widget "fraction" property to 0.1 (1/10, i.e. 10%). Following this each time the step sub-command is called, the widget bar will expand in length by 10% until it reaches 100%. The step sub-command accepts an additional argument which will set the text content of the bar.

    set modules [list \
        apple.tcl \
        blackberry.tcl \
        cherry.tcl \
        damson.tcl \
        elderberry.tcl \
        fig.tcl \
        gooseberry.tcl \
        hawthorn.tcl]
   
    proc do_progress { box modules } {
   
    set steps [llength $modules]

    set pb [gnocl::progressBar]
    $pb configure -steps $steps -showText 1
   
    $box add $pb
    $pb reset
   
    for {set i 0} {$i <= $steps} {incr i} {
        after 300
        $pb step [lindex $modules $i]
    }
   
    if ( [$box class] == statusBar ) {
        $box unpack $pb
    } else {
        $box remove $pb
    }
   
    }

In the above example, the reset subcommand was used to set the display fraction to 0.0 and text to and empty string.

More complicated operations, such as sifting through a large number of database records, may only need indication of relative progress. In other words, specific feedback on each increment in the batch process is not required. In this case the incr sub-command should be used. As with step above, an optional string can be specified, but if this field is left empty and the widget -showText option set to 1, the percentage completion of the bar will be displayed.

set range [ expr 1000 + round (rand() * 10000) ]
set steps 20
$pb3 configure -steps $steps -range $range -showText 1

for {set i 0 } {$i < $range} {incr i} {
    # do something or delay
    after 1
    $pb3 incr
   
}

Comments

Popular posts from this blog

gnocl::calendar

Given this module some attention today. Added some of the more package wide options to the module and created customised handler for setting the month. (For some odd reason months are are counted 0-11 whereas days are 1-31.) There's still a little more to do to this one including the addition of code to store diary details. Here's the working test script to show the range of options at work. The percentage substitution string item %e explores something that I've been toying with, the name of the signal/event that initiated the call. Ok, a script can keep its own internal trace but who knows, it might prove useful. #--------------- # calendarTest.tcl #--------------- # Author:   William J Giddings # Date:     07/05/09 #--------------- #!/bin/sh # the next line restarts using tclsh \ exec tclsh "$0" "$@" #--------------- package require Gnocl set cal [gnocl::calendar] $cal configure -day 8 -month 7 -year 1956 $cal configure -rowHeight 1 -colWidth 1 $ca

Gnocl Dashboard

Over the past few programming sessions I've been working on producing a central point, a dashboard, around which it's possible to see the various Gnocl widgets and commands in operation. In many ways like the demo script which shipped with the earlier releases of Gnocl but offers much more. The introspection functionality provides details of the various options and sub-commands of each Gnocl procedure which are displayed under the associated tab. Sample scripts are included for each item which offers newcomers a clearer insight into how make the most of what's on offer.

Simple Runtime Debugging Message Dialog

At times it's useful to see what values variables hold, or offer some pause point before the code goes elsewhere before causing havoc. Its possible to write output to the terminal but this can get lost in copious forms of other outputs, besides, there's no pausing the script execution either. The following proc creates a custom dialog which displays ad message along with the point in the calling script from which it was invoked. ## simple runtime debugging feedback dialog, alternative to console based gnocl::msg # @param msg message to display # @returns none # proc xxx::msg {txt} { set frame [info frame -1] append msg "Message:\n\n" append msg " $txt \n\n\n" append msg "Called from:\n\n" append msg "Proc:\t[lindex [info level -1] 0]\n" append msg "File:\t[file tail [dict get $frame file]]\n" append msg "Line:\t[dict get $frame line]\n" gnocl::dialog \ -type info \ -text $msg