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

[Bill S. <g4...@cl...>]

On 03/12/2015 23:35, Greg Troxel wrote:
> I didn't understand that rigctl now turns off AI.
It has too because the unsolicited AI traffic causes havoc with CAT 
conversations. There are flushes in pertinent places but collision 
handling is not up to dealing with AI traffic in all situations,

I know that there is some code for handing event driven changes but IMHO 
this will never work in a generic "virtual rig" model like that Hamlib 
uses because not all rigs broadcast and even the ones that do don't 
broadcast everything so there would have to be lots of background CAT 
polling to detect all possible events :(

I suppose that there could be some sort of registration for particular 
event types like frequency/mode/bandwidth/vfo/... changes in the public 
API but that would need every back end reporting what would need polling 
as opposed to AI mode providing. Gets very messy very quickly.

Just putting the patch together for turning off AI restore via a rigctl 
command line option. It is actioned by a new API fn so clients could use 
it as well if they really want to exit with a specified AI state.

73
Bill
G4WJS.