The handling of TPave options was incorrect. #17151
Merged
Conversation
This file contains 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
Test Results 18 files 18 suites 3d 18h 41m 39s ⏱️ Results for commit 917cfe6. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The handling of TPave options differed between
TPave::PaintPaveandTPave::PaintPaveArc. Specifically, inTPave::PaintPaveArc, the absence of one of the drawing options (TR,TL,BR, orBL) caused an incorrect shadow that completely obscured the TPave rendering. To address this, the default value when no valid drawing option is specified has been set toBR. Additionally, theNBoption (no border) is now processed as documented in theTPave::Paintheader.