96
Wayland Protocol 1.38 released (lists.freedesktop.org)
submitted 2 years ago by to c/linux@lemmy.ml
18 comments fedilink hide all child comments
 

This full packed release comes with three new staging protocols:

  • system bell - allowing e.g. terminal emulators to hand off system bell alerts to the compositor for among other things accessibility purposes

  • fifo - for implementing first in first out surface content update behavior

  • commit timing - for adding time constraints to surface content update

Other than this, the presentation timing protocol protocol got a version minor bump describing how to deal with variable refresh rate.

Other protocols saw the regular clarifications and bug fixes, and some deprecated events is now properly indicated as such in the XML. Please see individual commits for details.

all 18 comments

sorted by: hot top controversial new old
[–] 23 points 2 years ago

FIFO and commit timing are big for gaming. IIRC the lack of those protocols was a big reason why devs didn't want to enable Wayland support for SDL3 at first.

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 2 years ago (16 children)

    Focus solely on implementing session saving when?

  • permalink
  • fedilink
  • source
  • hideshow 16 child comments
    •
  • [–] 10 points 2 years ago (13 children)

    not a wayland dev but: patches welcome

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 2 points 2 years ago (12 children)

    Sure but I think the core devs should focus on it. It is a big thing that is important (especially for a piece of always changing beta software like Wayland) yet still missing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 12 child comments
    •
  • [–] 18 points 2 years ago (7 children)

    we all have our most wanted missing features but if i'm being honest i don't see how session saving should take priority over e.g. rendering protocols

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 2 years ago (6 children)

    What's wrong with rendering? It seems to have everything needed for most users. Driver issues don't exactly count here because they're not a part of Wayland. However session saving is very important for any work, especially office tasks. It's becoming critical now when all major DEs make Wayland the default.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 20 points 2 years ago (1 child)

    What’s wrong with rendering?

    Oh I dunno, maybe something with almost 700 comments? (HDR).

    However session saving is very important for any work, especially office tasks. It’s becoming critical now when all major DEs make Wayland the default.

    If apps don't want to save their state when they close there isn't much a window manager can do about that. The only part the window manager would be involved in is with positioning its window and that is hardly something very critical to the functionality of an app.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 10 points 2 years ago (3 children)

    Variable refresh rates. HDR. Colour management.

    ...for starters.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 years ago (3 children)

    Well the first step would probably be to open an issue.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 years ago (2 children)

    It's being worked on for years (or even decades lol). I highly doubt there isn't an opened issue about it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •