Skip to main content

List Row Colouration - Formatting a row of text in a list widget.



The way in which the tree and list widgets handle cell formatting is to emphasize data groups in the context a columns, and their background colouration. Specific cells are usually formatted based upon their contents, principally as foreground attributes although cell value contents can also be formatted using pango markup.


Row formatting in comparison is principally used for assisting visibility such as changing alternating row colour hinting and treeline. Selected rows are temporarily highlighted. Unlike the column configuration options Gtk+ offers no equivalent for setting rows attributes. To achieve this, each cell value needs to be reset and specific attributes assigned. The following example shows how to set the foreground colour for cells in the same row. 


#!/bin/sh
#\
exec tclsh "$0" "$@"
package require Gnocl

#---------------
# create UI
#---------------
proc main {} {
set box [gnocl::box -orientation vertical]
set ::list [gnocl::list \
    -titles {"string" "string" "string" "string"} \
    -types {string string string string} ]
$box add $::list -fill {1 1} -expand 1
gnocl::window -child $box -setSize 0.25
$::list add {0 "list widget" -104 1.45} -singleRow 1
$::list add {1 "window box" 3350 9.58} -singleRow 1
$::list add {AAA BBB CCC DDD} -singleRow 1

$::list columnConfigure 1 -editable 1

}

main

proc colorRowInit {wid {from 0} {to end}} {
    global _activeRow
    if { $to == "end" } { set to [$wid columns] }
    for { set i $from } { $i < $to } { incr i } { $wid columnConfigure $i -onCellData {setColor2 %w %p %v} }
    set _activeRow ""
       
    #---------------
    # change entry colour
    #---------------
    proc setColor2 { wid row val } {
        global _activeRow
        if { $row == $_activeRow } {
            return "-foreground red "
        } else {
            return "-foreground [list [$wid cget -textColor]] "
        }
    }
     gnocl::update
}
proc colorRow {wid row} {
    global _activeRow   
    set _activeRow $row
    for {set i 0} {$i < [$wid columns] } { incr i } {
        $wid cellConfigure $row $i -value [$wid get $row $i]
    }
    $wid draw
    gnocl::update
}


colorRowInit $list
set _activeRow 0
while 1 {
    after 1000
    colorRow $list $_activeRow
    
    if { [incr _activeRow] == [$list rows] } { set _activeRow 0 }
    
}


Comments

Post a Comment

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
7 comments
Read more

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.
6 comments
Read more

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
Post a Comment
Read more