ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
amadaluzia has quit []
glennk has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
Hypfer has quit [Ping timeout: 480 seconds]
olivial has quit [Remote host closed the connection]
olivial has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
the_sea_peoples has quit [Remote host closed the connection]
the_sea_peoples has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Quit: Konversation terminated!]
glennk has quit [Ping timeout: 480 seconds]
Spawns_Carpeting has quit []
Spawns_Carpeting has joined #wayland
atticf has quit [Ping timeout: 480 seconds]
the_sea_peoples has quit [Ping timeout: 480 seconds]
blueberrysnake4501140 has joined #wayland
atticf has joined #wayland
blueberrysnake450114 has quit [Ping timeout: 480 seconds]
kts has joined #wayland
Hypfer has joined #wayland
kts has quit [Quit: Konversation terminated!]
kts has joined #wayland
alarumbe has quit []
kts has quit [Quit: Konversation terminated!]
the_sea_peoples has joined #wayland
gallo has quit [Quit: Lost terminal]
gallo has joined #wayland
kts has joined #wayland
kts has quit []
leon-anavi has joined #wayland
sima has joined #wayland
rasterman has joined #wayland
bookworm_ has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
tzimmermann has joined #wayland
amadaluzia has joined #wayland
MrCooper_ has joined #wayland
MrCooper has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
the_sea_peoples has quit [Ping timeout: 480 seconds]
mahkoh has quit [Remote host closed the connection]
mahkoh has joined #wayland
kts has quit [Quit: Konversation terminated!]
Moprius has quit []
fmuellner has quit [Read error: Connection reset by peer]
fmuellner has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
feaneron has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
feaneron has joined #wayland
amadaluzia has quit [Ping timeout: 480 seconds]
amadaluzia has joined #wayland
kode545 is now known as kode54
<raiguard>
What is the "ideal" workflow for deciding on window dimensions on startup? From what I can tell, well-behaving clients appear to have some default resolution, but a well-behaving compositor will constrain that if it is larger than the output, then the client will remember the last-used size. Is this more-or-less correct?
<raiguard>
Unfortunately, GNOME appears to constrain the size to the size of all combined outputs instead of the output that the client is opened on.
<raiguard>
Actually, GNOME doesn't constrain the window size at all, it just maximizes it. When I un-maximize the window it restores to the 1920x1080 default, which is too large for the output.
sima has quit [Ping timeout: 480 seconds]
<raiguard>
Remembering the last-used window size doesn't make as much sense for a video game as it does for "regular" apps... so I would like to avoid that.
<jadahl>
raiguard: use xdg_toplevel.configure_bounds() which is the maximum size. what is "ideal" fully depends on the needs of your client.
<jadahl>
what you're seeing in GNOME is probably the result of `org.gnome.mutter auto-maximize` being on by default, which auto-maximizes things that are almost the size of the bounds
<raiguard>
Hmm, that appears to be what I need. I will have to discuss with SDL to get an SDL function to query that information.
sima has joined #wayland
mvlad has quit [Remote host closed the connection]
<raiguard>
Plasma will automatically constrain the client size to the output dimensions if it is too large without relying on maximize, which I think is a sensible solution.
<raiguard>
But I will still attempt to get xdg_toplevel.configure_bounds() implemented in SDL.