Describe the feature
The original BITMAPINFOHEADER is one of the most common bitmap headers, likely due to its combination of simplicity, versatility, and every header after it being much like a version with more stuff. Additionally it is very good for learning how bitmaps work, likely due to, once again, its simplicity.
Describe the expected behavior
It can (entirely losslessly) convert from (many) other image formats and from raw rgb/rgba data, but the main conversion happens from the latter. regardless of the starting point, the finish point is a BITMAPINFOHEADER-headed BMP file. if converting from an image, it will reuse the dimensions, bit depth, and bit layout of that image, and if not, it will calculate the first two manually and use preset options for the second.
Provide reference implementations
I'm not sure of any existing implementations that specifically use BITMAPINFOHEADER (if i haven't mentioned it already, the header that appears to be used here is BITMAPINFOV5HEADER). references on the format (in general) are available here and here, with the first one being my main source of information on how this specific header works.
Do you plan on implementing this yourself?
#704
Additional context
I did a bit of a search on issues before making this one and found that #148 could be related if I am able to add support for a custom palette in addition to the default one i currently have set up (as well as more compression options i suppose). letting @cs-deathmatch know.
Describe the feature
The original BITMAPINFOHEADER is one of the most common bitmap headers, likely due to its combination of simplicity, versatility, and every header after it being much like a version with more stuff. Additionally it is very good for learning how bitmaps work, likely due to, once again, its simplicity.
Describe the expected behavior
It can (entirely losslessly) convert from (many) other image formats and from raw rgb/rgba data, but the main conversion happens from the latter. regardless of the starting point, the finish point is a BITMAPINFOHEADER-headed BMP file. if converting from an image, it will reuse the dimensions, bit depth, and bit layout of that image, and if not, it will calculate the first two manually and use preset options for the second.
Provide reference implementations
I'm not sure of any existing implementations that specifically use BITMAPINFOHEADER (if i haven't mentioned it already, the header that appears to be used here is BITMAPINFOV5HEADER). references on the format (in general) are available here and here, with the first one being my main source of information on how this specific header works.
Do you plan on implementing this yourself?
#704
Additional context
I did a bit of a search on issues before making this one and found that #148 could be related if I am able to add support for a custom palette in addition to the default one i currently have set up (as well as more compression options i suppose). letting @cs-deathmatch know.