Skip to main content

Entry widget revisted

Some really useful feedback from John C. over the weekend drew my attention back to the gnocl::entry widget. I remember adding some extra bindings to it last year in a attempt to put the framework together for input validation and actualisation. One or two minor items were left undo which John picked up on. Thanks. I’ve some development scripts that I was working on at the time which I’ll drag out again. Now that the bindings are sorted, an undo/redo framework could also be implemented for the entry. So much to do, so little time to do it in!
What I did have time for though was to update the gnocl::entry docs page, the gnocl::signalStop command and add a simple tutorial on how to best use the gnocl signal/event bindings.
Then, after working on that, I returned for some coding on the pixBuf filters package. Created a handler to set filterparams using a struct, which, although it has reduced the module size considerably, it now begins to crash! C’est la vie!
Oh, and yes. Last night I thought that I’d build and test the abiwidget stuff. Downloaded it ok, and the dependencies but then the build process came to a halt after an hour! I’ll take another look at it in May.

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