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
Since #52 the wl_surface is not committed directly but it is left to GTK to do it if necessary.
However, it seems that in some cases, like when negative (or large enough) margins are set so that the surface leaves the screen, a direct commit is needed to make it come back. See WayfireWM/wayfire#1656.
Forcing a direct commit also solves a similar problem I reported for Labwc a little while ago: labwc/labwc#499.
The text was updated successfully, but these errors were encountered:
Yes, what's happening is the surface isn't getting a .frame wayland event, so GTK isn't committing. I think setting _GdkWindowImplWayland::pending_commit to TRUE (via the system we already have to access private GTK internals) might fix the problem, need to investigate more.
I think I'm experiencing this issue. I am using Flutter with gtk-layer-shell to make a virtual keyboard and after the initial render, the surface isn't updating. Any updates on this?
Since #52 the wl_surface is not committed directly but it is left to GTK to do it if necessary.
However, it seems that in some cases, like when negative (or large enough) margins are set so that the surface leaves the screen, a direct commit is needed to make it come back. See WayfireWM/wayfire#1656.
Forcing a direct commit also solves a similar problem I reported for Labwc a little while ago: labwc/labwc#499.
The text was updated successfully, but these errors were encountered: