Repository navigation
Expose page-object graphics state to external callers - #92
Open
magicismight wants to merge 1 commit into
Open
magicismight wants to merge 1 commit into
magicismight wants to merge 1 commit into
Conversation
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
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.
PDFium stores page-object alpha, blend modes, soft-mask state, Form transparency-group flags, and miter limits internally, but external callers cannot consistently read these properties through the public API.
FPDFPageObj_HasTransparency()combines several distinct conditions into one boolean, and color getters cannot expose alpha for objects without color state.External callers should be able to inspect these properties independently of color availability, without modifying the document or depending on private PDFium headers.