ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
MadcapJake has joined #wayland
ultra has quit [Quit: Ultra]
ultra has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
fmuellner has quit [Ping timeout: 480 seconds]
zvarde1988303206779191688 has joined #wayland
zvarde198830320677919168 has quit [Ping timeout: 480 seconds]
zvarde1988303206779191688 is now known as zvarde198830320677919168
abeltramo5 has quit [Read error: Connection reset by peer]
abeltramo58 has joined #wayland
zvarde1988303206779191688 has joined #wayland
zvarde198830320677919168 has quit [Ping timeout: 480 seconds]
zvarde1988303206779191688 is now known as zvarde198830320677919168
<pq>
anyway, I'll pass, I hope they get back in github
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
<Max1>
MrCooper: I've experimented a bit with XWayland, and I managed to get it non-blurry on a HiDPI monitor by manually passing the physical resolution via `-geometry` and starting it with `-fullscreen`
<Max1>
Because it uses wp_viewporter, everything works just fine then
<Max1>
Ah, and -dpi 192 looked a bit weird and was ignored by Chrome (which is what I want to run with XWayland), so I just left the X DPI settings untouched and started Chrome with --force-device-scale-factor=2
rv1sr has joined #wayland
<Max1>
Thanks again for your help :)
<Max1>
I think it should be possible to also use wp_viewporter when not in fullscreen, but I haven't tried it
<Max1>
Maybe I should file an issue so that someone who actually knows their way around the code can give it a try?
nerdopolis has quit [Remote host closed the connection]
kts has joined #wayland
tzafrir_laptop has quit [Quit: Quassel quit queasily, quoting Quixotic quip]
kts has quit [Quit: Konversation terminated!]
pochu has quit [Quit: leaving]
tzimmermann has quit [Quit: Leaving]
kts has joined #wayland
kts has quit []
zvarde198830320677919168 has quit [Remote host closed the connection]
zvarde198830320677919168 has joined #wayland
tzafrir_laptop has joined #wayland
junaid has quit [Remote host closed the connection]
cmichael has quit [Quit: Leaving]
agd5f_ has quit []
agd5f has joined #wayland
Major_Biscuit has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
Fxzxmic has quit [Quit: Konversation exit!]
molinari has joined #wayland
danshick_ has quit [Ping timeout: 480 seconds]
Major_Biscuit has quit [Ping timeout: 480 seconds]
danshick has joined #wayland
<DodoGTA>
Would a Wayland protocol for Xorg-style atoms be possible? Wayscope (Wayland gamescope) would likely require this kind of functionality
<ifreund>
it's been proposed and rejected a million times
<Shimmy[m]>
<DodoGTA> "Would a Wayland protocol for..." <- Isn't gamescope already a Wayland gamescope?
Brainium has joined #wayland
<DodoGTA>
Shimmy[m]: Gamescope still uses Xorg (in the form of XWayland) heavily (there's some basic Wayland support, but it's nowhere near good enough)
<bl4ckb0ne>
might be easier to move the whole gaming industry to wayland
<llyyr>
wine-wayland works sometimes
<DodoGTA>
The quality of varmd's code is not the best though (so I use the Alexandros' driver instead)