You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading a tag that fits into the offset field and is of type SHORT (Tiff type 3) the value is returned as Value::Unsigned instead of Value::Short.
This makes sense to fix, though the annoying part is figuring out whether anywhere else in the code is relying on the current behavior. Or whether it is likely to break any downstream users and thus might warrant additional caution
Regarding side effects I would suppose anyone interfering with the TAG data directly might have colliding types. What use case brought you to this, @lgpasquale ?
I suppose taking care of SSHORT is needed as well? This would require introducing an additional Value:
Adding support for SSHORT (i16) and SBYTE (i8) at #234, I can try to add the patches for the casting of SHORT as i32 instead of u32 in a follow up PR if there's interest?
When reading a tag that fits into the offset field and is of type
SHORT
(Tiff type 3) the value is returned asValue::Unsigned
instead ofValue::Short
.I believe the issue lies in line 407 of ifd.rs.
The right behavior is what can be seen when multiple values are handled (line 475 of ifd.rs)
The text was updated successfully, but these errors were encountered: