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.

  • GolfNovemberUniform@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    2 months ago

    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.

    • beleza pura@lemmy.eco.br
      link
      fedilink
      arrow-up
      19
      ·
      2 months ago

      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

      • GolfNovemberUniform@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        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.

        • NekkoDroid@programming.dev
          link
          fedilink
          arrow-up
          21
          ·
          2 months ago

          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.