Done some work with working on the print settings module today. Now, up to a little under 1100 lines of code and rising! I think that this will end up being one of the largest single modules once all the options are taken into account. Properly implemented the framework for setting print settings from basic options. I've got the basics ready for a 'settings get' subcommand too. Since Gtk+2.10 there has also been the option to save/load settings as a keyfile. This is also something that I'll take a look at. The current work on the print.c module means that the printoperation.c module is no longer needed and will be removed.
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
Comments