Skip to main content

PrintSetup, progress continues....

Did more work yesterday on the printsetup module. This has taken me more time than I expected for a couple of reasons. Firstly, the documentation surrounding the printing features is a little spartan. It needs time to sit and reflect upon what’s going on rather than having a simple ‘how-to’ set of instructions. I have a copy of Krause who does give a worked example, but it appears to me that the chapter on printing was not given the attention of other sections of his textbook. Secondly, for a number of reasons I’ve had little restorative sleep over the past few days and looking at the source code was a bit like trying to read sand! Yesterday was a better day, completed the conversion to using a param structure for the object registration. So far, so good.


In operation this should allow two ways of setting up a printer, explicitly through the script or interactively through the a dialog.


Something which did occur to me as a result of working on this was returning to the builder module in the future in order to see how it would be possible to convert a Glade defined widget such as a GtkEntry into a gnocl::entry. It would, be simply a matter of retaining the Gnocl name of the widget and redirecting the GtkEntry pointer in the instance of the EntryParams structure to point to the builder generated entry. Could be a pile of spaghetti, but should be interesting.



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