Re: [Hamlib-developer] Proper API implementation for Rotor-EZ

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

* Stephane Fillod <f8...@fr...> [2003 Feb 26 18:05 -0600]:
> If a protocol has no provision for rot_move, well the backend is not
> obliged to implement it. I would say, rot_move is for rotators who cannot
> implement rig_set_position.

Ahhh, so they are complimentary.  Why didn't I think of that?  :-\

> easycomm has both. Just implement what the protocol can do and
> that should do it.

It's working, so I won't change rotorez.

> Sure, you'd be very welcome!

I'll do that.  I'm hacking rotorez again now that some spare time has
returned.  

When I get this done I can get back to the ft920.  Sometime, hopefully 
by the next century or so, I'll have the '920 mostly complete.  I did 
what I thought were a bunch of code cleanups in ft920.c and hopefully 
caught a few bugs that were in earlier revisions.  So far no one has 
complained. :-)

I have not yet had a chance to test the code since you made the change
to RIG_VFO_CURR, but I don't think it should be a problem...

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