Skip to main content

{{{} {}}} What!

This level of nested braces may appear to be something from a programming quiz but, actually, this is meaningful when adding new, empty rows to a gnocl::list widget.

Suppose an instance of a list widget is created with 2 columns containing plain text.

set lv(s) [gnocl::list \
    
-types [list string string] \
    -titles {Keys Mapping}]

Appending new rows to the table is achieved using the widget subcommand add.  

$lv(s) add ...
 

So, adding an empty row can be achieved using

$lv(s) add {{{} {}}}

The widget code expects a list of rows, with each member of this list itself being a list whose items correspond to the column entries. Sounds kind of confusing and complicated. Well, it is. Especially when empty rows are being added.

Lets work our way our way through it, from the inside out.

The list has two columns, and lets take the following as our staring point. We will write these items to the cells to be appended.

col-1 col-2

A list of two items. This needs to be converted to a list for the row, simply done with braces.

{col-1 col-2}

And, as only one row it to be added, this list forms a single entry if the list of rows.

{{col-1 col-2}}

If the data entries contains white space, then these would need to be surrounded by braces or quotes. So,

{{{col 1}  {col 2}}}

Is the same as:

{{"col 1" "col 2"}}

Just to prove the point, lets add two rows.

{ {{r1c1} {r1c2}} {{r2c1} {r2c2}}}


All this single line bracing, especially with empty fields,  has just been something to capture the imagination. The previous line could also have been written much more clearly as:

{
{ {r1c1} {r1c2} }
{ {r2c1} {r2c2} }
}

So, we can now see, that 

{{{} {}}}

Is nothing other than:

{

{{} {}}

}

The addition of empty cells into 1 row, with 2 columns.




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

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

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.