ninja
ninja
I will push a branch later with my fixes. Right now my next priority to fix is the `opaque` mode not fully working...gnome thinks it's transparent and breaks screenshots...
I was also able to finally fix the screenshot problem issue...what a debugging hell it was... It's choosing wrong EGL config. It should choose one without alpha bits and then...
@christianrauch why did you remove surface commit from setSurfaceOpaque? I can't see any difference in resize performance, but it looked like a bug to me
did you change something specific yesterday? hard to know when you force push every time.. anyway feel free to review #1725
> It is not required and introduced resize glitches. If you want an opaque surface, request an XRGB buffer or an EGL configuration without alpha channel. What compositor are you...
@christianrauch if only we could prove that mutter treats XRGB buffers and opaque hint as equals and it won't hit performance...because I've never seen any app or framework skip calls...
@jadahl right, that's what I adressed in https://github.com/glfw/glfw/pull/1725/commits/2227df83f032ee7868c39fc983749a3fcdc22c7b I think. Maybe we could skip setOpaque then completly
what's the status of this? :)
@ewtoombs I am currently taking care of wayland fixes so I might be interested in taking over this one as well :thinking: Do you think this should be an opt-in...
> It is not a smoothness fix, but a latency fix, capable of reducing the mouse to screen latency by around a whole frame. Smoothness will be unaffected if all...