Skip to content

[BUG] bad handling of u8 data in saveImage #3544

Description

@syurkevi

saveImage should have explicit asserts for non-floating point data types. Saving u8 data through saveImage will result in corrupt image output from freeimage due to preprocessing steps. Either u8 data type needs to be preprocessed correctly or have explicit type checks to dissallow u8. Documentation needs to be updated to reflect allowable permutations of types and ranges, add differentiation between saveImage and saveImageNative()

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions