trimental
trimental
@fschutt both fixes are still needed despite the changes from the `positioned_words` branch. Filtering out refresh events may be intentional however it causes the problem of the window not appearing...
@neyb I’d happily update this PR to master. Unfortunately it seems that this PR is considered inadequate for the moment, which is fair enough considering it changes the Refresh event...
@christianparpart Yes you're completely right in all of those assumptions, ie we still need to render when the compositor is presenting previews or behind semi transparent windows. On macOS both...
@kchibisov done :)
@chrisduerr I was not able to replicate this issue with another gtk wayland application and @lovesegfault reports it to be fixed with FF 67. I think this was likely to...
@physkets can you run with the env variable WAYLAND_DEBUG=1 That would be more descriptive of the error then RUST_BACKTRACE due to it being a wayland event loop issue
Whilst Wayland introduces this clipboard problem for the rest of the ecosystem. I personally believe Wayland handles the clipboard in a more strict and 'correct' way, and other platforms are...
Sorry for chiming in with an idea on something I know little about; but could you do timer based rendering by having a vector of each unique monitor refresh rate...
Perhaps the reason why it takes time to reach the desired frame rate is because it works better when the windows intervals become desynchronised?