Consistent GLFW backend detection on hybrid Wayland/X11 systems

[mortacious]

On linux systems where the glfw library supports both X11 and Wayland (e.g. the universal libglfw3 package), get_x11_window and get_x11_display are present as attributes even when glfw is actually running on the Wayland backend. The old detection logic relied solely on hasattr(glfw, "get_x11_window"), which incorrectly selected the X11 path and caused a TypeError: ... crash because get_x11_display() returned None.

This replaces the attribute check with a runtime probe of the actual display handles: get_wayland_display() is called first; get_x11_display() is only called when Wayland returns None. Both calls are wrapped in warnings.catch_warnings(ignore, GLFWError) to suppress "X11: Platform not initialized" / "Wayland: Platform not initialized" warnings from glfw.

[almarklein]

Thanks! Great PR.

I think it makes sense to drop the api_is_wayland flag, and move the logic at the top of the module inside the get_glfw_present_info() function. So we have one clear point where the triage happens. What do you think?

[mortacious]

Thanks! Great PR.

I think it makes sense to drop the api_is_wayland flag, and move the logic at the top of the module inside the get_glfw_present_info() function. So we have one clear point where the triage happens. What do you think?

Yes, the import-time checks are actually quite useless now, since they are executed again at runtime anyway.

[almarklein]

Awesome, thanks!

[almarklein]

I'll do some tests when I have access to my Linux box soon.