Skip to main content

gnocl::pixBuf #3

Another busy and productive day. With the help fo Tadej at GtkForum I solved the problem of setting the fill colour values. The resulting function used to convert the colour values to the right format is:

static guint32 convertRGBtoPixel ( gchar *clr )
{
GdkColor color;
guint32 pixel;
/* Conversion factor from 16-bit color to 8-bit color (0xff / 0xffff) */
const gdouble f = 0.00389105;
/* create the colour from the supplied string, added by WJG */
gdk_color_parse ( clr, &color );
/* fill with colour */
pixel = ( ( ( guint ) ( color.red * f + 0.5 ) ) << 24 ) | /* R */
( ( ( guint ) ( color.green * f + 0.5 ) ) << 16 ) | /* G */
( ( ( guint ) ( color.blue * f + 0.5 ) ) << 8 ) | /* B */
( 0xff << 0 ); /* A */
return pixel;
}

Of all the obscure things that I've had to work through, the above bitshuffling and base alterations leaves me dumfounded. 

The key functionality added today then includes:

pixbuf commands
   turn
   flip
   rotate
commands
   load

Which will sorta have the following options:

   turn <(int) 0 | 90 | 270 | 180 | -90 | -180 | -270>
   flip -orientation <(str) horizontal (default) | vertical>
   rotate -angle <(dbl) angle> -backgroundColor <(str) colour>

The code for producing the arbitrary rotation is taken from zfuncs. The edge appears aliased and there may be better implementations but this should be sufficient for screen opts.

Other things that I acquired was a pdf of Phillips (1994) Image Processing in C. Gosh it is old. There's a Tcl/Tk front end to the library. Tell it was the published in the days before Python, Ruby and the rise of Perl. Tcl/Tk was 'hot' in those days. Today.....

Also got a nice new desktop today, an Acer Aspire X1301. Its largely to replace my old tower box which, with its many whiring fans sounds like a washing machine on full spin. The new machine, apart from being much higher spec is almost silent -magic! I haven't tried it myself yet but my daughter Georgie has been using it for most of the evening. She unpacked it, set it up and completed the OS installation. Not bad for a nine year old!

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