But unlike LoadCoefficients, "UpdateROI" cannot be set to 0, so it is always set at 1.
I think that here again, this is a documentation problem :
I have juste checked that indeed, the CoefficientsBuffer ROI seems to be taken into account (regarding the fps), after writing 1 into UpdateROI *even if the value is already 1*
Do you confirm ?
Should it be the case, I also heavily suggest that the documentation of UpdateROI is updated to explain that !
For instance, in my own GUI, since UpdateROI has only a single possible value, no GUI event is raised if I rewrite "1" in the associated NumericUpDown control, and thus I do not propagate to the Sgc_setIntegerValue(). That's why I got tricked !
It means that I should call Sgc_setxxxValue() even if the new value is the same as the current one.