From 0f9cc900d2a2a12629f18e848a1a6c218153403f Mon Sep 17 00:00:00 2001 From: Jack Jamison Date: Fri, 8 Aug 2025 21:46:01 -0400 Subject: improve grammar --- zola-static/content/blog/sdl-native-wayland.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zola-static/content/blog/sdl-native-wayland.md b/zola-static/content/blog/sdl-native-wayland.md index 3842800..ffbf4c7 100644 --- a/zola-static/content/blog/sdl-native-wayland.md +++ b/zola-static/content/blog/sdl-native-wayland.md @@ -9,7 +9,7 @@ updated = 2025-08-08 Here's the thing. X11 apps can still run under Wayland through the XWayland compatibility layer. In the [SDL3 documentation](https://wiki.libsdl.org/SDL3/README-wayland) it says that > Wayland is a replacement for the X11 window system protocol and architecture and is favored over X11 by default in SDL3 -However if your compositor does not implement the `wp_fifo_manager_v1` protocol, SDL will fall back to XWayland. I don't know the details how this protocol fits into the Wayland ecosystem but my compositor doesn't have it. Here's how I forced SDL to use Wayland anyway (for c++). +However, if your compositor does not implement the `wp_fifo_manager_v1` protocol SDL will fall back to XWayland. I don't know how this protocol fits into the Wayland ecosystem, but my compositor doesn't have it. Here's how I forced SDL to use Wayland anyway (for c++). ```c++ for (int i = 0; i < SDL_GetNumVideoDrivers(); i++) { if (std::string(SDL_GetVideoDriver(i)) == "wayland") { @@ -18,5 +18,5 @@ for (int i = 0; i < SDL_GetNumVideoDrivers(); i++) { } } ``` -This code will explicitly enable Wayland if it is available. Thanks to my friend Riley Beckett for helping to figure it out. +This code will explicitly enable Wayland if it is available. Thanks to my friend Riley Beckett for helping figure it out. > I [asked about this issue](https://discourse.libsdl.org/t/is-wayland-really-default) on the SDL discourse. -- cgit v1.2.3