Re: [Hamlib-developer] what's up?

[<rs...@su...>]

On Thu, 11 Oct 2001, Stephane Fillod wrote:

> 	You'll need automake 1.5. Otherwise, you may have a chance
>  in regenerating all the .in files.

automake && ./configure && make install
works. Strange.

> > Sorry, but I still haven't tested our IC275 and 475 at home. Have to find
> > the old self-built interface first and then visit mom (DK3XJ) :)
> >
>   Great! She will be happy to see you, but first wait IC275 and 475
>   are added..

Oops... isn't it a C-IV device as well? I really have to get that stuff
out of the box on the shelf :-)

> 	Let me know if some functions are missing in Hamlib, or if you
>   think the design is not appropriate. Accessing the caps/state directly is
>   recommanded, instead set_conf/get_conf should be used, provided more
>   parameters are declared (yet to be done). Maybe there should be some
>   config data file support in Hamlib, regardless the application.
>   What do you think?

I am trying to figure out why kdevelop wants to have -fno-exceptions in
the CXXFLAGS. Any ideas? I removed it manually from configure, so now I
can at least compile with <hamlib/rigclass.h> included.

Kontakt has an own static class RigCaps with member functions that do a
get_rig_caps(rig_model_t) and return one specific value: A few
things I need to show the user before selecting a device: mfg_name,
model_name, rig_type, and a QString containing a textual representation of
the status (alpha, ...). Or does hamlib(++) already supply this and I
missed it?

Config file in hamlib: I think the user would get too much "involved" with
the lib, which should only be a background thing for the "real app". The
user should be able to install a new rpm at any time without having to
look for some config file somewhere. And, he has to do some settings in
the application anyway, so put it all in there, even though he will have
to enter the same data once(!) in each app.

How do I find out which device need which specific settings? Like
baudrate, target IP address, etc. What is the struct confparams in rig.h?
I am focussing completely on the <hamlib/*.h> includes and not really
reading the hamlib source much (stupid app writers shouldn't have to
anyway :))

>   Yep, as soon as I have downloaded the 8MB+ for the qt upgrade...

Which upgrade? This is Qt2-stuff, I'm not using Qt3 here.

Enough for today, more tmrw.

73, Robert
-- 
Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
http://1409.org                                   ro...@st...