Announcement

Collapse
No announcement yet.

PCSX2 Emulator Disables Wayland Support By Default

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by varikonniemi View Post

    Show me one GNU based Android release? LEt alone one used by billions.


    "Indeed, just about the only component in common between Android and GNU/Linux is Linux, the kernel"

    crocodile tears that they didn't use all your shitty software and are multiple orders of magnitude more successful.

    See the OA for the reasons why.

    Wayland and Surface Flinger both depend on EGL/GLES btw, which is where all the "hard work" gets done.

    Last edited by mSparks; 27 November 2023, 07:31 AM.

    Comment


    • #62
      Originally posted by yoshi314 View Post

      well, he is the guy who arguably did the most work for pcsx2 in the recent year or two. vulkan suport, new qt gui and a lot of performance improvements are all his work.

      That, and he's the dev of duckstation.
      Yes but thesubpar CSD implementation is Qts fault.

      Comment


      • #63
        Originally posted by Gusar View Post
        Rule 1 when dealing with Wayland: Ignore Gnome. Seriously. mpv has been doing it for years. Just inform the user:

        No window decoration? Gnome doesn't support the xdg-decoration protocol. Screen goes blank while watching a video? Gnome doesn't support the idle-inhibit protocol. They actually do nowadays I think, but for years they didn't. The correct cursor doesn't show when hovering mpv? It's cos Gnome has its own special way to handle cursors that isn't compatible with anything else.


        Rule 2 when dealing with Wayland: See if wlr protocols can help you. The wlr-layer-shell protocol provides some form of window positioning, could cover what pcsx2 needs. But this only works with wlroots, you say? Nope, kwin and even mir support wlr protocols.


        Now, the above won't fix everything in regards to dealing with Wayland, but it will make your job a lot easier already.
        yup, everything is at least a bit better when we ignore gnome

        Comment


        • #64
          The GNOME way of doing CSD is an inconsistent mess, where you suddenly have a Confirmation button where on other windows the X is placed.
          A confirmation button is the exact opposite of what an X does. GNOME CSD is just as bad as those internet ads that want to trick you to click on them by faking UI elements.

          Comment


          • #65
            Originally posted by Quackdoc View Post

            yup, everything is at least a bit better when we ignore gnome
            Right, ignore the only Wayland desktop environment that offers the most consistent experience where most things just "work" properly, while having the largest install base among desktop Linux.

            Zoom desktop client for Linux even explicitly targets Gnome for remote screen control over Wayland. Sure, go ahead and ignore Gnome.

            Comment


            • #66
              Originally posted by mSparks View Post



              "Indeed, just about the only component in common between Android and GNU/Linux is Linux, the kernel"

              crocodile tears that they didn't use all your shitty software and are multiple orders of magnitude more successful.

              See the OA for the reasons why.

              Wayland and Surface Flinger both depend on EGL/GLES btw, which is where all the "hard work" gets done.

              https://android.googlesource.com/pla...urfaceflinger/
              You forgot ChromeOS, which has only the bare minimum of GNU stuff but is still wildly more successful than any desktop Linux distribution.

              Comment


              • #67
                Originally posted by Sonadow View Post

                Right, ignore the only Wayland desktop environment that offers the most consistent experience where most things just "work" properly, while having the largest install base among desktop Linux.

                Zoom desktop client for Linux even explicitly targets Gnome for remote screen control over Wayland. Sure, go ahead and ignore Gnome.
                Zoom's a funny one. Made with Qt for universal operating support while using internal GNOME APIs because they mostly only target GNOME-based distributions. Their only outliers are Arch (can run GNOME) and Mint (forked GNOME).

                Comment


                • #68
                  Originally posted by Sonadow View Post

                  Right, ignore the only Wayland desktop environment that offers the most consistent experience where most things just "work" properly, while having the largest install base among desktop Linux.

                  Zoom desktop client for Linux even explicitly targets Gnome for remote screen control over Wayland. Sure, go ahead and ignore Gnome.
                  bro, I cant even get an OSK that properly supports gnome wlroots and kde fuck outta here with the "just work" bullshit, just because your stuff works doesn't mean everyone's does. wayland has more fragmentation then a grenade does

                  Comment


                  • #69
                    Originally posted by Quackdoc View Post

                    bro, I cant even get an OSK that properly supports gnome wlroots and kde fuck outta here with the "just work" bullshit, just because your stuff works doesn't mean everyone's does. wayland has more fragmentation then a grenade does
                    That's the problem with the compositor and not Wayland the protocol. Blame Gnome, Plasma and Sway for not getting it right even after a decade into Wayland.

                    Whatever your complaints are, Gnome is still the most performant and usable Wayland desktop environment to date compared to the other two.

                    Comment


                    • #70
                      Originally posted by skeevy420 View Post

                      Zoom's a funny one. Made with Qt for universal operating support while using internal GNOME APIs because they mostly only target GNOME-based distributions. Their only outliers are Arch (can run GNOME) and Mint (forked GNOME).
                      The fact Gnome has these internal APIs is proof it's entirely possible for a compositor to do what needs to be done for all these sore points about screen sharing and control under Wayland. There's nothing to stop Plasma and wlroots from following suit.

                      If desktop Linux would finally wake up and converge on these three compositors as the Wayland compositors for Linux, many of these problems will have been solved by now.

                      I rather deal with three internal APIs *now* and start selling my products *now* than wait another 7 years for these three internal APIs to finally become one common API.
                      Last edited by Sonadow; 27 November 2023, 09:30 AM.

                      Comment

                      Working...
                      X