[Hamlib-developer] rig.h

[Dale E. E. <de...@w-...>]

Stephane,

I added my rig.h to the CVS.  I tried removing the stuff that depended
upon
having changes in rig.h but ended up with a rig that just gave
-RIG_EINVAL
for just about everything.  Also, you said two things that stuck in my
mind:
        1) make sure I'm confident of the changes
        2) CVS will allow us to back out the changes if required.

The stuff I was doing to as work-arounds lowered my confidence in what
the changes would do.  I have visited all of the backends and I'm almost

certain there will be little if any effects from my changes.

The kylix (and any file that duplicates rig.h) should be considered
broken.
I've only glanced at the kylix stuff.  Some of it may actually be
unaffected
but I need to go line-by-line and make sure it gets updated (and stuff
like
tcl, etc...).

Everything compiles after checking it back out (had to run automake on
the kenwood directory and check the new Makefile.*'s in).

The only test I could think to perform was rpcrig.   I tried that for
the first time
and it worked perfectly!  I only used 'v', 'F',  and'f' but for a quick
check it
was quite a thrill.  My two computers are connected via ethernet and the

rig on the serial port worked well.

Let me know if something actually breaks that I didn't expect.  I'll be
working
fast a furious to get the stuff I know about matching rig.h.

I'd appreciate it if you give me a chance to fix any problems that may
arise
and not just back out the new revisions.  The download stats reported by

SourceForge are fairly low,  you just a new release, and judging by
the CVS dates there is not a lot of activity at the moment.

There's not much more I can do to boost my confidence that things will
work except commit to CVS and start working on kylix as soon as I get
a little sleep.

Thank you in advance.  Now that I have things working (from my point
of view) I can do more towards rewriting and bringing things in-line
with
the "standard" code.

73's

Dale
kd7eni