Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New attributes: fill-opacity, stroke-opacity #248

Open
tkvogt opened this issue Apr 24, 2015 · 6 comments
Open

New attributes: fill-opacity, stroke-opacity #248

tkvogt opened this issue Apr 24, 2015 · 6 comments
Assignees

Comments

@tkvogt
Copy link
Member

tkvogt commented Apr 24, 2015

SVG differentiates between fill-opacity and stroke-opacity. It would be handy to have this for the svg parser in diagrams-input. Of course this could be implemented by overlaying two diagrams: One where fill is mempty and one where the outline linewidth is set to 0. But this depends on solving issue issue 247.

@cchalmers
Copy link
Member

The fill and stroke opacities can be different by chaining the opacity of the AlphaColour Double in their Texture.

@tkvogt
Copy link
Member Author

tkvogt commented Apr 24, 2015

Can you give me an example how to set the fill and stroke opacity separately?

@cchalmers
Copy link
Member

Hmm, if you want to set just the fill opacity for everything in a diagram after you're already set the fill colour, that would be more difficult. If you know the fill opacity when you're setting the fill colour it's just fcA (c withOpacity o).

@byorgey
Copy link
Member

byorgey commented Sep 11, 2015

@tkvogt Is this still an issue, or did you figure out a workaround?

@tkvogt
Copy link
Member Author

tkvogt commented Sep 12, 2015

Am 11.09.2015 um 22:59 schrieb Brent Yorgey:

@tkvogt https://github.com/tkvogt Is this still an issue, or did you
figure out a workaround?


Reply to this email directly or view it on GitHub
#248 (comment).

There is no workaround. These attributes are necessary for a perfect
loading of SVG images. But this only makes every 10th image look bad.
Could someone of you implement this? I am not so fluent in diagrams
internals.
It reminds me that I have to finish diagrams-input, mention it in
diagrams-manual an upload it to hackage.

@byorgey
Copy link
Member

byorgey commented Sep 14, 2015

I don't think this should be too hard to implement. The hardest part will just be changing backends to support it. But that can be done incrementally. I will see if I can get around to this sometime soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants