Re: [Hamlib-developer] CQ CQ hamlib-developers..

[Frank S. <vk...@ix...>]

Stephane Fillod wrote:
> 
> On Sun, Apr 22, 2001, Frank Singleton wrote:
> > >
> > > > Does my yaesu stuff still compile  ok ?
> >
> > Actually, I ran it against my FT747 anf FT847 and it all looked
> > ok .
> 
> Did you ran the last commited version (sunday)?

Hmm  I used the latest CVS prior to sending this original email
response.


> It got the new VFO id design (that can be OR'ed), and pbwidth_t is now
> the filter width in Hz passed to set_mode et al. Grep RIG_PASSBAND_OLDTIME
> and FIXME in the code to see where to update.
> 
> >
> > Yes I agree. But I have an intersting idea .............
> >
>   Sounds like there's some CORBA or RPC in the air....
> 

I have been thinking about that also ....... :-)
Stay tuned !

> [snip]
> > This  way, I dont go blind trying to fill the correct line in the
> > rig_caps struct
> > for a certain function pointer,or freq range list, and I dont care what
> > order they are listed.
> 
> hmm, but it makes code harder to write (type castings, etc.), slowing
> down your app because of lookups, loosing type checking, etc.
> 

lookups probably not too bad (cache hits ) but the type checking
is definitely good to keep , I agree..

> > This way, I dont have to jump over "NULL" entries etc..
> 
> If this is all what's worring you, just follow the winradio/wr1500.c
> example. It makes the code a lot easier to read!
> 

> So what else do we need for an 1.1.1 release?
> Add a couple of set_split_mode and get_split_mode, rig_send_cw,
> remove chan_qty, dtmf_digits, ..
> Any idea?

Let me check it this weekend ..

/Frank..


-- 
Cheers / Frank 

73's de vk3fcs & km5ws