Skip to main content

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
$cal configure -monthChange 1
$cal configure -dayNames 1
$cal configure -details 1
$cal configure -heading 1
$cal configure -weekNumbers 1
$cal configure -font {Courier 12}
$cal configure -baseColor #ffffdd
$cal configure -sensitive 1
$cal configure -visible 1
$cal configure -tooltip "Calendar"

$cal configure -onDaySelected {puts "%e %d %m %y"}

$cal configure -onDoubleDaySelected {
    puts " %e %d %m %y"
    %w detail add -date [list %d %m %y] -text {birthday}
    }

$cal configure -onMonthChanged {puts "%e %d %m %y"}
$cal configure -onNextMonth {puts "%e %d %m %y"}
$cal configure -onNextYear {puts "%e %d %m %y"}
$cal configure -onPrevMonth {puts "%e %d %m %y"}
$cal configure -onPrevYear {puts "%e %d %m %y"}

gnocl::window -child $cal -title gnocl::calendar

gnocl::mainLoop

Comments

criskross said…
Hello,

i am even not getting it to run. I nearly tried each Version of Gnocl but i am always getting:

% gnocl::calendar
configure
demonstrate_details
calendar_update_details -1
calendar_update_details -2
calendar_update_details -3
calendar_get_detail -1
calendar_get_detail -2
calendar_get_detail -3
calendar_update_details -4
Segmentation fault

Where is the fault?
1:07 pm
criskross said…
Hi i am always getting problems when i am trying to create a set cal [gnocl::calendar]

configure
demonstrate_details
calendar_update_details -1
calendar_update_details -2
calendar_update_details -3
calendar_get_detail -1
calendar_get_detail -2
calendar_get_detail -3
calendar_update_details -4
Segmentation fault


Where is the Problem? I nearly tried each nightlyBuild and als binaries
1:13 pm
William J Giddings said…
Hi Crisskross

Basically, the instructions which you've applied are not valid.

The segmentatation fault is arising from the interpreter trying to handle these instructions.

WJG
2:24 pm
criskross said…
First of all thx for the fast reply. :)

What do you mean with not valid?

when i am trying to set t with:

set t [gnocl::calendar]

i am getting the following errors:

configure
demonstrate_details
calendar_update_details -1
calendar_update_details -2
calendar_update_details -3
calendar_get_detail -1
calendar_get_detail -2
calendar_get_detail -3
calendar_update_details -4
Segmentation fault

So what do you mean with the interpreter?
2:54 pm
William J Giddings said…
In that case I'm not sure where the problems are coming from. The test script given above still works on my machine even with the current build.

If this information is being output to the console then it looks like some the debugging comments typically generated. If this is the case, then the segmentation fault may be arising from a bad printf/g_print command in the sources.

I'll take at the sources look this evening.
4:25 pm
criskross said…
Hello, did you find some errors?
9:14 am
William J Giddings said…
I've tidied up the debug comments and so these should not interefere with your scripting.

I get no runtime errors at all.

The calendar implementation still needs a whole pile of work doing on it. Its ok, for selecting dates, but the Gtk+ widget has much more to offer, i.e data display.
11:20 pm
Post a Comment

Popular posts from this blog

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