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 Wayland event loop pretty much implements our MainLoop interfaces - timers, signal watches, fd watches. When interacting with Wayland it's almost always necessary to do so from the Wayland event loop, so currently when we want to watch a file descriptor and then do something on the Wayland loop, or set a timer to do something on the Wayland loop we need to first set the timer, and then from the callback push another callback into the WaylandExecutor that can then be run on the Wayland loop.
Instead we could just have a Wayland-main-loop-backed implementation of MainLoop that does everything on the event loop, making everything cleaner.
The text was updated successfully, but these errors were encountered:
The Wayland event loop pretty much implements our
MainLoop
interfaces - timers, signal watches, fd watches. When interacting with Wayland it's almost always necessary to do so from the Wayland event loop, so currently when we want to watch a file descriptor and then do something on the Wayland loop, or set a timer to do something on the Wayland loop we need to first set the timer, and then from the callback push another callback into theWaylandExecutor
that can then be run on the Wayland loop.Instead we could just have a Wayland-main-loop-backed implementation of
MainLoop
that does everything on the event loop, making everything cleaner.The text was updated successfully, but these errors were encountered: