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
The renderer is changing framebuffer alpha (for the parts under the mouse cursor), expecting it to be ignored (even though nothing in the code explicitly only allows framebuffers with no alpha), similar to Ultimaker/Cura#8466https://stackoverflow.com/q/35245809
(the right side actually looks fully yellow on screen, the glitches are only on screenshots… and the fact that the behavior is different on the left and right sides of the screen suggests some kind of HiDPI issue somewhere?)
The text was updated successfully, but these errors were encountered:
valpackett
changed the title
Hovered part rendering transparency issue (on Wayland)
Hovered/selected part rendering transparency issue (on Wayland)
May 9, 2021
This looks a difficult problem to solve as it is highly platform specific. Meanwhile, just in case you don't know, you can disable Preselection highlight, Preselection on top, and Selection on top to prevent the object goes transparent.
I still haven't figured out how to do it in Qt, but generally it's trivial to request a framebuffer without alpha. e.g. aap/librw#35 in GLFW it's just glfwWindowHint(GLFW_ALPHA_BITS, 0) and that's it
The renderer is changing framebuffer alpha (for the parts under the mouse cursor), expecting it to be ignored (even though nothing in the code explicitly only allows framebuffers with no alpha), similar to Ultimaker/Cura#8466 https://stackoverflow.com/q/35245809
(the right side actually looks fully yellow on screen, the glitches are only on screenshots… and the fact that the behavior is different on the left and right sides of the screen suggests some kind of HiDPI issue somewhere?)
The text was updated successfully, but these errors were encountered: