ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
co1umbarius has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
columbarius has quit [Ping timeout: 480 seconds]
<pounce>
hey folks, _really_ don't want to start a CSD flamewar, but is there anything I can link to which describes the state of CSD/SSD in the wayland space?
<pounce>
e.g. which compositors support SSD and which don't
<i509VCB>
wayland.app recently added a compositor support field for protocol listings, more compositors could be listed and data gathered for
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
caveman has joined #wayland
<DemiMarie>
Some compositors not only support SSD, they force them
<DemiMarie>
And others only support CAD. So as a client developer you need to support both cases.
<DemiMarie>
s/CAD/CSD/
dcz_ has joined #wayland
WhizzWr has joined #wayland
hardening has joined #wayland
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
<pounce>
DemiMarie: right, exactly. i just wanted to add this context to a github issue about CSD
caveman has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
danvet has joined #wayland
immibis has quit [Ping timeout: 480 seconds]
<i509VCB>
Even in the case where a compositor may force an option, it's still compositor policy. For example I could let alacritty use ssds and then force everything else to csds
tzimmermann has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
<pq>
Sesse, I believe there was intention to emulate an actual video mode change. If you set an actual 640x480 mode on a 1024x768 CRT, that will strecth too, right?
<Sesse>
yes
<Sesse>
but usually on a 1280x720 LCD, you'd get pillarboxing
<pq>
I believe that depends on the LCD settings.
<pq>
ISTR seeing options for everything: 1:1 pixel pillarboxing (centered), aspect ratio strecthed + black bars, strecthed without aspect ratio
<pq>
so it's an end user setting in the real hardware
<Sesse>
sure. but seemingly not configurable in xwayland.
<pq>
how that maps to the Xwayland emulation design I'm not sure - hm, ofourdan isn't here.
<pq>
Xwayland is not configurable, yes
<pq>
depending on how Xwayland does things, it might be configurable in the Wayland compositor
<Sesse>
and from a client application, it's not trivial to get the desired behavior
<pq>
well, you can't
<pq>
like you could not in the real hardware era with Xorg, right?
<Sesse>
well, in theory I could render internally to 640x480, then stretch+pillarbox myself
<Sesse>
well, in the real hardware era, everything was 4:3 anyway =)
<pq>
Sesse, I believe ofourdan would know more. In any case, any configurability outside of changing the app would be in the Wayland compositor you use.
<Sesse>
sure
remyabel2 has joined #wayland
remyabel2 has quit []
remyabel2 has joined #wayland
ofourdan has joined #wayland
<MrCooper>
Sesse: a wild ofourdan appeared!
<ofourdan>
hehe
<Sesse>
perhaps someone used the irc /summon command
<MrCooper>
something like that :)
<ofourdan>
what was the question again?
<emersion>
ofourdan: do you have any plans for a wayland-info release?
<ofourdan>
no plan, but we could make one anytime
<Sesse>
ofourdan: backing up a few kilometers: I have an old X11 app (2004-era) that I'm trying to update for semi-modern computers, and one of the things it does is that it sets the videomode to 640x480 and opens a fullscreen window
<Sesse>
which causes the 4:3 window to be stretched to my 16:9 display in xwayland
<Sesse>
whereas it would be much nicer to pillarbox it
<Sesse>
(making it wayland-native is not an option at this time, because reasons)
<emersion>
ofourdan: there are a few unreleased commits queued up, so would be nice
<ofourdan>
alright will do
<emersion>
cool, let me know if i can help
remyabel2 has quit [Remote host closed the connection]
<MrCooper>
Sesse: AFAICT it's hardcoded like that in Xwayland and would need to be changed there (which I agree would be a good change)
<Sesse>
yes, looks pretty hardcoded
remyabel2 has joined #wayland
<ofourdan>
it's the viewport's doing, pretty much on purpose
<ofourdan>
does Xorg behave any different when foprcing a 4:3 rsolution on a 16:10 monitor?
<Sesse>
well, we discussed it briefly, and I think the answer is “maybe”
<Sesse>
ie., largely displays on the monitor and settings
<pq>
monitor OSD settings can usually be used to choose what the monitor does, it's not about Xorg
<ofourdan>
that would be you monitor, not Xorg itself
<Sesse>
yes
<Sesse>
so I mean, Xorg doesn't actually deal with this
<ofourdan>
because Xorg *sets* the resolution (unlike Xwayland) and the monitor can adjust
<Sesse>
indeed
<pq>
xdg-shell fullscreen window mode has provisions for the compositor to choose how to handle a smaller-than-screen fullscreen window, but that doesn't help Xwayland
<ofourdan>
exactly, because it doesn't use fullscren, but viewports
<pq>
...or could have, I forget the actual spec
<emersion>
some monitors might stretch, some monitors might add pillar-boxing
<Sesse>
I have no idea what the difference between fullscreen and a viewport is in wayland parlance
<emersion>
when using a mode which doesn't have the same aspect-ratio as the monitor
<emersion>
it depends on the mode, EDID has some hints about it
<ofourdan>
Sesse: basically, Xwayland has no control over your hardware, not even the monitor resolution, so it *emulates* Xrandr using viewports to /zoom/ the actual window to fit the size of the monitor
<Sesse>
yes, that's what I figured as well
<pq>
ofourdan, would this have to be a Xwayland-specific atom/property on the X11 window to control the type of viewporter scaling, so XWM (i.e. the Wayland compositor) could control it?
<Sesse>
ofourdan: can I set an arbitrary resolution here?
<Sesse>
instead of just the modelines I get back
<Sesse>
if so, I could just invent a 16:9 resolution, and pillarbox myself