ICO encoder: Write 1 color plane#3043
Merged
Merged
Conversation
197g
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
According to Wikipedia, "Setting the color planes to 0 or 1 is treated equivalently by the operating system". However, I found that there are edge cases where 0 and 1 are not treated equally and only 1 is accepted (the size fallback from #3042 only seems to trigger if
wPlanesis 1). The correspondingbiPlanesinBITMAPINFOHEADERis also required to 1.For those reasons, I think our encoder should emit 1 for color planes for best compatibility. This PR implements that.