Quote:
Originally Posted by RileyC3826
Thanks, I think I understand what you mean, but I cannot deploy new code and test it right now due to windows updates on our driverstation laptop, I will reply back if/when I get a chance to test some changes.
|
The issue has been resolved! By switching '!pipeline.filterContoursOutput().isEmpty()' to 'pipeline.filterContoursOutput().size >= 2', the program does stop when only one target is visible, but the numbers resume updating when both targets are back in view. The updated code has been committed directly to the code on GitHub which I linked earlier. This code could be further modified to allow values to update when one target is visible.