Skip to main content

Cloning a Gnocl Widget Made Simple

A while ago I saw a StackoverFlow request about cloning widgets. Ok, the request was about cloning Gtk widgets in C, but here's the solution in Tcl using the Gnocl package. For a some time now its been possible to query the Gnocl package about the various options and commands available to each widget and its this ability combined with the cget (configuration get) command that allows property and data values to be extracted from a widget. Here's a very simple example based upon a button. 



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

if { [catch { package present Gnocl } ] } { package require Gnocl }

## clone specified widget
#/param    wid the widget to clone
#/returns   wid of newly created clone object

#
proc gnocl::clone { wid } {
               
        foreach item [split [string trim [gnocl::[$wid class] options]] \n] {
                # get list of options from internal help,
                # trim away option information
                set item [string range $item 0 [string first " " $item]-1]
                lappend res $item [$wid cget $item]
        }
       
        return [gnocl::[$wid class] {*}$res]
}

## test proc

#
proc main { } {

        set but [gnocl::button -text %#New -onClicked { puts "HIDIHI" } ]
       
        gnocl::window -child $but \
              -x 500 -y 500 -width 300 -title ORIGINAL
        gnocl::window -child [gnocl::clone $but] \
              -x 850 -y 500 -width 300 -title CLONE
       
}

main

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.

Getting Widget Style Properties

Until the move over to Gtk4, Gnocl is still built against the Gtk 2.21 libraries. One of the inconveniences of Gtk is getting and setting widget style settings which are considered to be set globally by the desktop style settings and not for the programmer to tinker around with. Needless to say, there are times when different defaults are preferred, largely to draw the users attention to 'something a bit different'. The function gtk_widget_modify_font  is a convenience function to set the widget basefont as shown in this snippet from the button.c module,  if ( options[baseFontIdx].status == GNOCL_STATUS_CHANGED ) { GtkWidget *label; label = gnoclFindChild ( GTK_WIDGET ( para->button ), GTK_TYPE_LABEL ); PangoFontDescription *font_desc = pango_font_description_from_string ( Tcl_GetString ( options[baseFontIdx].val.obj ) ); gtk_widget_modify_font ( GTK_WIDGET ( label ), font_desc ); pango_font_description_free ( font_desc ); } Unfortunately, there's no d...