Re: [Hamlib-developer] Conflict with RIG_VFO_CURR and RIG_VFO_NONE

[Stephane F. <f8...@fr...>]

On Wed, Jan 08, 2003, Nate Bargmann wrote:
> As I'm working with the ft920 code to make it more robust, I am
> modifying rigctl to prompt for the VFO to read/set.  In so doing I am
> testing the return of parse_vfo for RIG_VFO_NONE.  Unfortunately, when I
> try to pass currVFO from rigctl, get_freq exits early as RIG_VFO_CURR
> and RIG_VFO_NONE are both defined in rig.h to 0!
> 
> How can this be rectified?  It seems that making RIG_VFO_CURR to be
> non-zero is the simplest answer.

okay, RIG_VFO_CURR has been allocated a non-zero value, it's in cvs.
Please let me know if it breaks anything for you. 
So far, with the new value, it's fine for me.

Cheers,
Stephane