fixed inference disruption problem #66
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally, the default value of "isInference" is 'false'. Whenever the component is rendered, the value of "isInference" is automatically set to false. So it appeared that when we switch out from and then back to "inference" tab, the "start inference" button is activated, as if the inference stopped.
In this update, the variable pair { isInference, setIsInference} is replaced by a new pair { isInferring, setIsInferring }. And they became the prop of the component . The value of "isInferring" is updated solely by "setIsInferring", not by any initializing default value. By this, the status of the "start inference" button is solely determined by the status of inferring.