This repository was archived by the owner on Oct 2, 2023. It is now read-only.
fix opacity issue in string options#9
Open
samvanderpoel wants to merge 1 commit into
Open
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This PR addresses a mismatch between the way opacity values are exported to TeX code and the way \filldraw expects to receive those values. Presently, opacity values are exported as their percentage values, e.g.
30, whereas TikZ expects to receive them in key-value pair format where the opacity is a decimal, e.g.opacity=0.30. This issue raised an error when attempting to compile a simple example whenopacityis notopaque.