Skip to main content

Text Widget List Viewer


 

 

The list widget is a great tool for displaying related information in sets. That is a sample, distributed across rows and columns. To do this the list widget creates cells for each sample and allocated memory to handle its formatting and data. In practice, this means two 'blocks' for each piece of data. The information to display, and how to display it.

This arrangement works fine for large humanly workable amounts of data, perhaps up to 1,500 or more rows. But, what about more, much, much more?

I have a translation data set with source and target language pairs well in excess of 57,000 pairs. The list widget will handle these, but the delay receiving and rendering is far too long. The solution then, is to tweak the text widget to handle similar rows with a row picker. Sounds complicated, but its not. Just a couple of tweaks needed. Put the text widget inside an eventBox and then trap any direct events being passed to it, whilst allowing the scrolledWindow container to get the input it needs.

Why do this? By default the text widget will change the mouse pointer to an edit bar. The eventBox retains use of the

Achieving the latter is the easiest, nothing required. The scrolledWindow takes priority over the eventBox by default. So, turn off the text cursor, and make it invisible and respond to the eventBox mouse button events to change the paragraph colour of the selected block -simples!

 


# !/bin/sh
# the next line restarts using tclsh \
exec tclsh "$0" "$@"

package require Gnocl


# ~~~~~~~~~~~~~~~~~~~~~~~~~~

set txt [gnocl::text -editable 0 -cursorVisible 0]
$txt tag create idx -paragraph orange

set ebox [gnocl::eventBox -child $txt -aboveChild 1]
gnocl::window -child $ebox -setSize 0.2


# add some text to the widget.
for {set i 0} {$i<250} {incr i} {
append buff "$i) Lorem\n"
append buff [gnocl::lorem]\n
}
$txt set $buff
puts [$txt getLineCount]


#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# SET EBOX EVENTS TO SIMULATE LINE SELECTION AND TEXT SCROLLING
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$ebox configure \
-onButtonRelease {
    %c tag remove start end -tags idx
    %c setCursor [%c getPos]
    %c tag apply lineStart lineEnd -tags idx
} \
-onScroll {
    if { "%D" == "down" } {
        incr ::scrollPos 5
            if { $::scrollPos > [%c getLineCount] } { set ::scrollPos [%c getLineCount]}
        } else {
            incr ::scrollPos -5
            if { $::scrollPos < 0 } { set ::scrollPos 0}
        }
    %c scrollToPosition "$::scrollPos 0"   
}
 


 

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

Creating a button box with right aligned widgets

The dialog widget has its own internal functionaluty to create and position buttons at the bottom right corner of the window container. When creating these for ourselves it must be born in mind that default settings for fill and expand are both 0.5. Failing to set these will always place the child objects in the centre, regardless of alignment. For most cases these defaults are acceptable but, to create that dialog-button arrangement, use the following snippet as a model!   # to right align completely, set expand and fill to 0 set hbox [gnocl::hBox] set b1 [gnocl::button -text Select \                -data $lst                 -onClicked { puts DO-SOMETHING-WITH-%d} ] set b2 [gnocl::button -text Cancel -onClicked { puts DONE! } ] $vbox add $hbox -expand 0 -fill 0 -align right $hbox add $b1 $hbox add $b2

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.