You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is related to glium/glium#1678. I'm absolutely not familiar with how OpenGL surfaces should interact with Wayland, but what I gathered is that the resulting alpha channel will affect the compositing of the window.
The glium backend uses the glium::Blend::alpha_blending() alpha blending function (
This commit:
* Fixes up the alpha blending draw parameters as discussed in
glium/glium#1844 and
PistonDevelopers/conrod#1347
* Introduces `colorize` and `colorize_hsv` functions to the shader.
comments in the code explain those functions in detail.
As of this commit, `colorize_hsv` is what is used now. To my
eye on this mac, it produces blended glyphs with less noticeable
dark antialiasing fringes.
refs: #470
I believe this is related to glium/glium#1678. I'm absolutely not familiar with how OpenGL surfaces should interact with Wayland, but what I gathered is that the resulting alpha channel will affect the compositing of the window.
The glium backend uses the
glium::Blend::alpha_blending()
alpha blending function (conrod/backends/conrod_glium/src/lib.rs
Line 294 in 351367e
srcAlpha * srcAlpha + dstAlpha * (1 - srcAlpha)
(https://github.com/glium/glium/blob/776413b4eb8da16a4e9801feb27754e400e7d25a/src/draw_parameters/blend.rs#L28). To me this seems really wrong. I believe the usual way of combining the alpha channels issrcAlpha + dstAlpha * (1 - srcAlpha)
, which means the code should be changed into this:However I do wonder if this should be fixed in glium by changing
glium::Blend::alpha_blending()
.The new blending function matches that of of the wgpu backend, which does not exhibit this issue.
The gfx backend, while it to does not appear to exhibit this issue, uses
gfx::preset::blend::ALPHA
which issrcAlpha + dstAlpha
, so it is also incorrect.The text was updated successfully, but these errors were encountered: