Ten days have passed since the release of grig 0.7 and I have not received any bug reports until today. Berndt, one of the BSD guys, has discovered that grig is not installable because $(DESTDIR)/share/grig is not created prior to attemting to copy files into the directory. Fortunately, this stuff is done as one of the last things during install, so the installation will work and only the README, ChangeLog and similar files will be missing. I fired up my laptop and could confirm the same behaviour on Suse Linux.
Grig
Everything related to grig.
Grig Goes 0.7
Two weeks ago I had a correspondence with Richard VK1RJ concerning some problems with the controlling the TenTec Pegasus. After examining the debug output it turned out that the hamlib backend was working all right but it didn’t set any initial values for the AF and RF levels leaving them at the default minimum level.
Grig Hits 0.6.0!
In the meantime I went on hacking on grig. Besides fixing the bugs mentioned last week I managed to finish the save/restore rig state functions. Currently, the state can only be loaded at runtime but I intend to add the possibility of loading .rig files from the command line as well. Furthermore, I have done … Read more
Grig Bug Hunt Night
Phew… what a rush! I found and fixed bug after bug after bug after bug… the worst ones were in the rig-daemon, where the read values were overwritten by the last set values every time the specific set command was executed. This was the case for PTT, POWER and FREQ, and so the old display flicker problem has been solved, too. 
hamlib/ft817.c: Power Levels
I’ve decided to look at the FT-817 backend tonight. There are some TODOs concerning the check of the TX level readings. I couldn’t do them before because I had only batteries to power the FT-817, thus tuning with 5W wasn’t really possible.
Grig Message Window
No radio this weekend so I could work on some software instead.
New Idea for Debug Handler
I have been thinking about the performance issues I have experienced in playing with the GtkListView based debug handler. I am sure that it will not work out the way I wanted because too many messages come in too fast when the debug level is set to RIG_DEBUG_VERBOSE or RIG_DEBUG_TRACE. Still, I think the idea of some tool to browse the debug messages is good.
The New Message Window
I have finished a protype of the new grig message window, which is part of the grig debug handler. The idea is to trap debug messages from hamlib and show them in a nice GtkListView and maybe also a GtkTreeView.
Response on the Hamlib Debug Handler
Today I received a reply from Stephane concerning my problems with the new hamlib debug handler api.
New Debug Handler in Hamlib
I have now tried to use the new debug handler API in hamlib but without any success. Some time ago, Stephane added some code to hamlib, which allows frontend programs to register their own debug handler, which then will be called every time a debug message is sent. The API uses the same parameter structure as the old hamlib API meaning that the handler will receive the comlete variable argument list that was originally sent to the rig_debug function.