From: Nate B. <n0...@ne...> - 2003-03-28 01:18:51
|
* Stephane Fillod <f8...@fr...> [2003 Mar 27 17:45 -0600]: > absolutely right. This is fixed now, commit should follow. Let me know > if there're other flaws or mistakes. Oh, you know me! I'm not afraid to fire off an email. :-) > yes, that would be cool, but being too smart add complexity. > It's better to keep the KISS approach. It was a thought. KISS is best, and this kind of behavior results in a lot work for the application using Hamlib, which we don't want to do. > In that case, I would recommand the use of rig_get_channel, with > an optimized backend. > > > The downside of this idea is that only ON/OFF values may be reported. > > How would we report multiple AGC values, for instance? > > rig_get_channel and levels. Hmmm, another thing to go off and learn...another day! > BTW Nate, your idea of allowing vfo target in rigctl is very good for > testing purpose. I took the liberty of extending it to other commands. > Just pass "-o" to rigctl when you want to specify the VFO. VFO_CURR will > apply otherwise. > I've also allocated 'Z' and 'z' to set_xit/get_xit. Sheepish grin. I didn't really intend for my private copy of rigctl to get out, but I had copied it over there for another reason and had forgotten it. That said, I've been able to exercise my backends with direct VFO access. The command option is an excellent implementation since both behaviors are now available. As well, you may have noticed that I replaced the character for Dumpcaps and a few others by numbers. The reason is that in my EN_us locale, all I got on the display was "?" characters. As we go along I'm wondering if two character commands could be added? 73, de Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | n0...@ne... | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto |