Skip to main content

Overhaul of widget cget functionality.

The current basis of the cget function for widgets is based upon code written over 20yrs ago and, whilst it works reasonably well for the simple setting of gtk widget properties, support for more complex custom options is hit and miss.

 

typedef struct GnoclOption_ {
    const char *optName;  
    enum GnoclOptionType type;
    const char *propName;
    gnoclOptFunc *func;
    const char *args;
    const char *description;
    const char *values; 
    enum GnoclOptionStatus status;
    union {
        gboolean b;
        gint     i;
        gdouble  d;
        gchar    *str;
        Tcl_Obj  *obj;
        } val;
} GnoclOption;

 

With the recent updating of the C sources which includes an expansion of the GnoclOption structure to accommodate documentation support, it well worth reviewing the way in which widget functions handle the return of options.

Rather than treating the retrieval of properties set by a function as the final call, perhaps it should be prioritized. If one is not present, then extract a value based upon the setting type. 

 case CgetIdx: {
 int     idx;

/* get the idx of the option in structure array */
Tcl_GetIndexFromObjStruct ( interp, objv[2], ( char ** ) &options[0].optName, sizeof ( GnoclOption ), "option", TCL_EXACT, &idx );

/* does the option have a function? */
if (options[idx].func != NULL) {
    Tcl_Obj *res;
    options[idx].func ( interp, &options[idx], grid, &res );
    Tcl_SetObjResult ( interp, res );
} else {
    switch ( gnoclCget ( interp, objc, objv, G_OBJECT ( grid ), options, &idx ) ) {
      case GNOCL_CGET_ERROR: { return TCL_ERROR; }
      case GNOCL_CGET_HANDLED: { return TCL_OK; }
      case GNOCL_CGET_NOTHANDLED: {
           return cget ( interp, grid, options, idx ); }
  }
}
break;
}
return TCL_OK;
}


Placing this test at the head of the sequence is more intuitive as these provide the greates complication when dealing with extraction of settings.

A GnoclOpFun woudl then be something along the lines of:


static int gnoclOptBaseLineRow ( Tcl_Interp * interp, GnoclOption * opt, GObject * obj, Tcl_Obj **ret )

{

gint idx;

Tcl_GetIndexFromObj ( interp, opt->val.obj, baseLinePositions, "baseLinePosition", TCL_EXACT, &idx );

if ( ret == NULL ) { /* set value */

g_object_set ( obj, opt->propName, idx, NULL );

} else { /* get value */

g_object_get ( obj, opt->propName, &idx, NULL );

Tcl_SetObjResult ( interp, Tcl_NewStringObj ( baseLinePositions[idx], -1 ) );

}

return TCL_OK;

}

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...