In our previous article, we covered user-facing Treeland upgrades for windows, gestures and multitasking.

Nevertheless, a genuinely usable desktop demands smooth execution of everyday applications — an unavoidable challenge.

Games, 3D programs and legacy X11-based software pose persistent compatibility challenges for Wayland-based desktops. These issues are less visually obvious than window animations, yet they directly determine whether your frequently-used software and games run properly on Treeland.

This article discusses recent progress on Treeland's application-compatibility front.

Treeland is a Wayland compositor developed by the deepin community. Built atop wlroots as its foundational Wayland library, Treeland leaves the upstream wlroots code untouched. This allows it to seamlessly sync with upstream updates, picking up new features and bug fixes in a timely manner. Its upper layer leverages Qt, unlocking access to a large pool of existing Qt developers. There is no longer a need to assign dedicated staff exclusively to this project, unifying DDE’s technology stack.

01 | Two Invisible but Critical Protocols

Consider two usage scenarios:

Scenario 1: While playing an FPS game, your mouse cursor escapes the game window. An accidental click on the desktop causes the game to lose focus.

Scenario 2: Rotating the viewport in 3Dmodelling software. The application needs relative mouse movement deltas rather than absolute screen coordinates to manipulate 3D objects.

These distinct use-cases depend on two core Wayland capabilities:

- pointer-constraints: restricts the mouse cursor within application window boundaries.

- relative-pointer: supplies applications with mouse movement offset instead of absolute position values.

In short, pointer-constraints locks the cursor inside windows; relative-pointer reports how far the mouse has moved.

These protocols are essential for functional FPS gameplay, responsive 3Dmodelling and professional design software. Treeland has advanced its implementation of both protocols.

End-users rarely perceive these protocols directly, yet their benefits become tangible when cursors stay confined inside game windows and 3D-viewport manipulation feels responsive.

02 | Xwayland: Indispensable Compatibility Layer

A full transition to Wayland cannot happen overnight. Countless legacy X11 applications must continue operating on Treeland.

Xwayland serves as this compatibility layer, enabling non-Wayland-native software to run under Wayland desktops. Better Xwayland stability and compatibility translate to more applications working out-of-the-box.

Treeland has recently resolved multiple Xwayland-related defects affecting window management, context menus and input focus. Individual bugs appear minor, yet cumulatively shape daily usability: reliable context-menu pop-ups, correct window switching and preventing keyboard input from going to the wrong window. Stable low-level details build overall desktop reliability.

03 | A Complete Chain: From Underlying Protocols to Real-World Applications

To recap the technical chain:

  • pointer-constraints and relative-pointer resolve core-interaction requirements for FPS titles and 3D professional software.
  • Ongoing Xwayland fixes maintain compatibility with a large number of legacy X11 applications.
  • Improvements to Wine's Wayland support help more Windows office applications run reliably on Treeland.

Across these three layers — low-level protocols, compatibility shims and enduser software — Treeland pursues one goal: ensuring your intended applications function correctly.

Polished animations and visual appeal attract users to try Treeland. Rich, usable, reliable applications convince them to stay.

Treeland aims for more than merely supporting additional applications. End-users seldom care about protocol names or low-level interfaces. Their practical concerns are straightforward: Can my games run? Will my required software work? Will everyday usage be trouble-free?

Treeland continuously narrows the gap between underlying technology and user expectations. The objective is to move from "applications can launch" to "applications run excellently", until users barely notice they are operating atop a new technical stack. This constitutes another major step from functional capability toward real-world usability.

The next article will examine system stability: reducing crashes and anomalies for multi-monitor configurations, input focus, Alt+Tab and drag-and-drop operations. Share your experiences on the deepin Forum.