The ext-image-capture-source-v1 and ext-image-copy-capture-v1 screen copy protocols build upon wlroots’ wlr-screencopy-unstable-v1 with various improvements for better screen capture support under Wayland. These new protocols should allow for better performance and window capturing support for use-cases around RDP/VNC remote desktop, screen sharing, and more.

Merge Request: Create ext-image-capture-source-v1 and ext-image-copy-capture-v1

  • Mactan@lemmy.ml
    link
    fedilink
    arrow-up
    31
    arrow-down
    4
    ·
    edit-2
    3 months ago

    under the definition of bike shedding in the Encyclopedia you’ll find wayland the prime example. been waiting years on one pr for them to decide on the word “may” vs “will”

    • gbin@lemmy.ca
      link
      fedilink
      arrow-up
      17
      arrow-down
      3
      ·
      3 months ago

      It drives me crazy. Just release it 18+months ago and iterate with versions, at least your users will have the feature in their hands.

        • gbin@lemmy.ca
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          3 months ago

          It is kind of shooting at the ambulance, zoom needs to also adapt to the new API. The alternative is a completely non functional Wayland for videoconferencing for years… Unusable stable is not better than unstable usable IMHO at least you have a shot at fixing it for the second option.

    • Vincent@feddit.nl
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      edit-2
      3 months ago

      decide on the word “may” vs “will”

      I assume they went with _way_land as a compromise.