Re: Cross-coupling comboboxes

On 07/06/2019 21:11, Rob Pearce wrote:
> And when it does so, the iterator returned by get_active() is invalid, 
> which my code doesn't test for in the secondary case, so that would be 
> worth doing... hold on... 

Yep, that seems to have fixed it.

There may be a better fix. It would be nice if calling clear() on the 
model didn't invoke the signal_changed of BOTH comboboxes 328 times each 
(I think I mentioned the selection is getting rather large) but as long 
as I return immediately if get_active() returns an invalid iterator then 
it doesn't cause problems.

Thanks for your help.