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
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
jmdaemon has quit [Quit: WeeChat 3.6]
cabal705 has joined #wayland
cabal704 has quit [Ping timeout: 480 seconds]
wills[m] has quit [autokilled: Spambot. Mail support@oftc.net if you think this is in error. (2022-09-04 01:03:12)]
cabal705 has quit [Read error: Connection reset by peer]
remyabel21 has quit [Remote host closed the connection]
remyabel21 has joined #wayland
cabal705 has joined #wayland
cabal705 has quit []
fmuellner has quit [Ping timeout: 480 seconds]
cabal704 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
cabal704 has joined #wayland
cool110 has quit [Ping timeout: 480 seconds]
cool110 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
cabal704 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
cabal704 has joined #wayland
cabal704 has quit [Read error: Connection reset by peer]
cabal704 has joined #wayland
Net147 has quit [Quit: Quit]
Net147 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
cabal704 has joined #wayland
remyabel21 has quit []
Net147 has quit []
Net147 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
cabal704 has joined #wayland
Net147 has quit [Quit: Quit]
Net147 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
cabal704 has joined #wayland
cabal704 has quit []
cabal704 has joined #wayland
riteo has joined #wayland
<riteo>
hiiii!
<riteo>
Does anybody know what the `serial` argument for `wl_data_offer::accept` is for?
<riteo>
I can find literally zero info about this argument
<riteo>
the docs literally describe it as "serial number of the accept request", which is entirely useless
nerdopolis has quit [Ping timeout: 480 seconds]
remyabel2 has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
remyabel2 has quit [Remote host closed the connection]
<riteo>
I think that the docs are wrong in this case
zebrag has quit [Read error: Connection reset by peer]
zebrag has joined #wayland
sozuba has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
dcz_ has joined #wayland
<DemiMarie>
What heuristics should tools like Wine use to work around Wayland’s restrictions? I would like to see some sort of semi-standardized heuristics, instead of every implementor having to start from scratch.
<kennylevinsen>
The heuristics are tied to whatever you are mapping from. What your options are for win32 may not relate to your options for macOS WindowServer or Xwayland.
<DemiMarie>
I suspect there are some general guidelines that could be useful, though.
<DemiMarie>
Things like, “Popup windows should be mapped to xdg_shell’s popup, with the absolute position replaced by the relative position to the apparent parent window.”
cvmn has quit [Remote host closed the connection]
cvmn has joined #wayland
danvet has joined #wayland
riteo has quit [Quit: epic a64 moment]
<kennylevinsen>
That is not the heuristics in question, just a simple subtraction
<kennylevinsen>
Heuristics in wine would be more like "detect that a window might be a popup based on it having been explicitly moved on top of another window in absolute coordinates prior to being realized"
<kennylevinsen>
"intentionally lie and space out windows in absolute coordinates to increase accuracy of the former"
<kennylevinsen>
Or something like that
<vyivel>
reading this makes me want to check wine-wayland
<kennylevinsen>
IIRC, a big chunk of wine being against Wayland at the beginning was due to Windows just using normal "windows" for everything, but yeah - seeing what they did and how for that got them would be better :P
<kennylevinsen>
That's the most recent popup heuristics. But dang, that branch has over 170 commits towards Wayland support. Makes the popup heuristic seem rather insignificant...
<vyivel>
>if...it's relatively small compared to the
<vyivel>
monitor size
<vyivel>
wew
hardening has joined #wayland
rasterman has joined #wayland
<DemiMarie>
Yikes
<DemiMarie>
Probably going to be a long stream of special cases
fmuellner has joined #wayland
sozuba has quit [Quit: sozuba]
<daniels>
Wine did need a couple of commits to work perfectly on X11 too
qyliss has quit [Quit: bye]
qyliss has joined #wayland
nerdopolis has joined #wayland
Lucretia has quit [Remote host closed the connection]
Lucretia has joined #wayland
luc4 has joined #wayland
gallo has quit []
cabal704 has joined #wayland
luc4 has quit []
<DemiMarie>
<daniels> "Wine did need a couple of..." <- How much harder is Wayland likely to be?
d42 has joined #wayland
bcheng has quit [Remote host closed the connection]
bcheng has joined #wayland
zebrag has joined #wayland
cabal704 has quit [Quit: WeeChat 3.5]
fmuellner has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
sozuba has joined #wayland
eroux has quit [Read error: Connection reset by peer]
eroux has joined #wayland
cabal704 has joined #wayland
andyrtr_ has joined #wayland
andyrtr has quit [Read error: Connection reset by peer]
andyrtr_ is now known as andyrtr
cabal704 has quit [Quit: WeeChat 3.5]
sozuba has quit [Quit: sozuba]
eroux_ has joined #wayland
cabal704 has joined #wayland
eroux has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]
zebrag has joined #wayland
sozuba has joined #wayland
Narrat has joined #wayland
scriptingdad[m] has joined #wayland
qyliss has quit [Quit: bye]
qyliss has joined #wayland
cvmn has quit [Remote host closed the connection]
cvmn has joined #wayland
cabal705 has joined #wayland
cabal704 has quit [Ping timeout: 480 seconds]
Sesse has joined #wayland
cabal705 has quit [Read error: Connection reset by peer]
<Sesse>
hi. is there any documentation about Xwayland's emulation of the XF86VMode extension? it seems to be heuristic-based, but it's not easy to figure out how to deal with aspect...
<kennylevinsen>
The code, mainly. What's the problem?
cabal705 has joined #wayland
<Sesse>
I set up 640x480 on a 1920x1080 screen, and it stretches
<Sesse>
instead of pillarboxing
<Sesse>
well, my 2004-era code does
<Sesse>
it seems to me as if the logic is something like: if you set a mode using XF86VidModeSwitchToMode(), it gets ignored, but if you then open a window that's the exact same size, it gets stretched to the full size of the display
<Sesse>
(except keyboard grab doesn't work, so it doesn't get any keyboard events, but that's a different story)
cabal705 has quit [Read error: Connection reset by peer]
cabal705 has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
dcz_ has quit [Ping timeout: 480 seconds]
<Sesse>
kennylevinsen: the code was a bit twisty, but it seems it indeed ignores aspect and just stretches
rv1sr has quit []
mbalmer has joined #wayland
mbalmer_ has quit [Ping timeout: 480 seconds]
sozuba has quit [Quit: sozuba]
cabal705 has quit []
buh0 has joined #wayland
buh0 has quit [Quit: Bye!]
AJ_Z0 has quit [Read error: Connection reset by peer]