Re: [Hamlib-developer] Pull Request: Restore AI on exit - needs testing

[Greg T. <gd...@le...>]

Bill Somerville <g4...@cl...> writes:

> On 03/12/2015 13:39, Greg Troxel wrote:
>> So basically I'm suggesting that save/restore be (possibly default)
>> behavior for the open/close sequence used by full-blown programs, and be
>> not the default for bare rigctl usage.   rigctl could have options
>>    --no-save-restore
>>    --save-restore
>> with one of them (I vote for --no) being default.
> Hi Greg,
>
> thanks for the thoughtful comments. I basically agree except that I
> think the default for the rigctl command line program should be
> --save-restore, my reasoning is that restoring AI mode is important to
> some devices like StepIR aerial controllers and some amplifiers that
> need band change information. Because of this and because a few rigs
> allow AI on by default we should not be silently turning AI mode off
> (the current behaviour). Any other application that needs AI turned
> off or on should do so on start up so the way we leave it is only
> important to these passive devices.
>
> I think it is reasonable for anyone who wishes to use rigctl to change
> the state of AI mode to have to specify --no-save-restore. The only
> issue is that it is a behavioural change for those that already use
> rigctl to change AI mode state. I suspect that there will be as many
> that no longer have to do anything at all as there are those that have
> to add a new command line switch.

I didn't understand that rigctl now turns off AI.  I thought the
save/restore for it was only to protect an explicit disabling.  So now I
can definitely see your point that --save-restore be default.

73 de n1dam