Re: [Hamlib-developer] vfo_t rewrite

[Nate B. <n0...@ne...>]

* Stephane Fillod <f8...@fr...> [2003 Mar 10 17:11 -0600]:

> * Split combinations are not to be handled here. We need to
>   create (or modify) an API call like the following:
>   rig_set_plit_vfo(RIG*, vfo_t rx_vfo, split_t split, vfo_t tx_vfo);
>   What do you think?

I like this, Stephane.  As I've been thinking about implementing
set_split_freq and friends for the FT-890, I've been conjuring up all
manner of nasty hacks.  I like this API.

Reading the rest of your message I gather that set_vfo is to be used to
set the rig into memory mode.  This does make sense, but I haven't
implemented that in either ft890 or ft920, yet.  Scanning further into
the API than I have in some time I see set/get_mem which appears to be
for setting/getting a specific memory channel.  So, I need to correct
set_vfo in each backend (what else is new?).

> Backend developers, please let me know if this new design does not let
> you describe what your rig can do.

I just wish the FT-920 could do through the CAT what it can do on the
front panel.  This isn't the fault of Hamlib, though.  :-(

Add to the wishlist some policy documentation, much like you're doing
with vfo_t.  In other words, the answers to most of my questions!

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