Fix initialization checks in Mat classes to handle '0' values #52
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.
Fix for
Mat
Initialization withCvType
ConstantsProblem:
When using certain
CvType
constant with a value of0
(CvType.CV_8U
), theMat
class was not initializing correctly due to truthy/falsy checks in the constructor.Solution:
Explicitly check for
undefined
values in theMat
class constructor to ensure that values like0
are treated as valid.Changes:
Mat
class constructor to explicitly check forundefined
.0
values correctly.Example:
The issue was evident when using the
CvType
constants: