James CalligerosJul 2

Users just want their computer to work with minimal fuss. They get told to try a Linux distro because it’s safer and faster than the alternatives, and the Linux desktop is totally ready for primetime now!

“Why do my games launch on my secondary vertical monitor? Why can’t I just pick a default monitor?”

“We aren’t implementing that because it’s from Windows. If you want your applications to launch on your main monitor go and use Windows.”

How the fuck can we expect to retain users when a nontrivial minority of developers seems totally fine treating them with such contempt?

Show threadLeeloo

@chadmed
Is that an actual quote, or is it made up FUD?

It doesn't sound real to me, but you never know.

A more probable explanation is that it's controlled by the game and we can't force the games to do the right thing. Or the game leaves it up to the window manager, which is why it's good to have multiple different window managers to choose from.

Jul 3 at 10:14amWeb
Show threadLeelooJul 3

@chadmed
In fact I've seen the exact opposite claim - years ago, auto detection of screen dpi was removed, and hard coded to 96 dpi. At the time, it was claimed that this was because that's what windows did.

Later I managed to find the real reason. The api in question only supported one dpi, but with multiple monitors, there is't one dpi. A compromise had to be made and that compromise ended up being 96 dpi. There is a newer api which gives the dpi per monitor, and that api still works.

Conclusion: Anyone can make up reasons for why something works a certain way, so unless you find a quote from the developers who made the decision, you can't trust the claim.

Show threadJames CalligerosJul 3
@leeloo https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/179
Output selection for games (#179) · Issues · wayland / wayland-protocols · GitLab

Game toolkits like SDL are in a bit of a difficult situation when it comes to selecting the output to place a fullscreen game on. The current way...

GitLab
Show threadLeelooJul 3

@chadmed
I do not see anything in that thread that matches your claim.

I see a lot of trying to figure out what the problem is, and several people arguing that it's SDL abusing the existing api, and as a result not getting the result they would have if they'd used the api correctly. Which of course a new API is not going to change.