ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
mclasen has quit [Ping timeout: 480 seconds]
kenny has joined #wayland
fmuellner_ has quit [Ping timeout: 480 seconds]
Bugies has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
Leopold_ has joined #wayland
tent405 has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
RAOF has quit [Remote host closed the connection]
RAOF has joined #wayland
gilvbp has joined #wayland
RAOF_ has joined #wayland
RAOF has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
Leopold__ has joined #wayland
Leopold_ has quit [Remote host closed the connection]
Leopold__ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
mxz has quit [Ping timeout: 480 seconds]
gilvbp has quit [Quit: Connection closed for inactivity]
mclasen has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
kts has joined #wayland
kts has quit [Remote host closed the connection]
kts has joined #wayland
mxz has joined #wayland
vincejv has quit [Quit: Bye bye! Leaving for now...]
zxrom has quit [Quit: Leaving]
JakeSays1 has joined #wayland
glennk has joined #wayland
JakeSays has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
garnacho has joined #wayland
<davidre>
whot: So what you are asking about mapping pointer buttons into the keymap to also produce syms eventually?
rooq9 has quit []
tzimmermann has joined #wayland
sima has joined #wayland
rooq9 has joined #wayland
qaqland has joined #wayland
mvlad has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
rgallaispou has quit [Read error: Connection reset by peer]
rgallaispou has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
Bugies has joined #wayland
glennk has joined #wayland
JakeSays has joined #wayland
selckin has quit [Quit: selckin]
JakeSays1 has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
karolherbst has quit [Quit: Konversation terminated!]
kts has quit [Ping timeout: 480 seconds]
Bugies has quit [Ping timeout: 480 seconds]
rgallaispou has quit [Read error: Connection reset by peer]
johnhalo has joined #wayland
johnhalo has quit []
zxrom has joined #wayland
fmuellner has joined #wayland
vincejv has joined #wayland
Brainium has joined #wayland
mclasen has joined #wayland
privacy has joined #wayland
Hypfer has quit [Read error: No route to host]
Hypfer has joined #wayland
kts has joined #wayland
Hypfer has quit [Read error: No route to host]
kts has quit []
Hypfer has joined #wayland
kts has joined #wayland
JakeSays1 has joined #wayland
JakeSays has quit [Ping timeout: 480 seconds]
mclasen has quit []
mclasen has joined #wayland
Bugies has joined #wayland
Leopold_ has quit [Remote host closed the connection]
bodiccea has quit [Ping timeout: 480 seconds]
rgallaispou has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
<DodoGTA>
What effect does XRRSetCrtcConfig() have with XWayland?
<ofourdan>
depends, Xwayland rootless has some XRandR emulation using wp_viewport for legacy fullscreen applications. For Xwayland rootful, it depends whether Xwayland rootful is running fullscreen or not. But the general rule is that it does nothing, because Xwayland is just a regular Wayland client and as such cannot change the actual resolution as this is managed exclusively by the Wayland compositor, which is
<ofourdan>
the "true" display server in charge.
<DodoGTA>
ofourdan: Apparently it doesn't even change the XRandR mode information (which some applications depend on)
<ofourdan>
that's normal
<ofourdan>
what mode information in particular?
<DodoGTA>
ofourdan: The current display mode (changing it with a simple xrandr command does nothing to that parameter)
<ofourdan>
Xwayland cannot chnage the mode, that's what I am saying. There is some heuristic to emulate mode change for some legacy X11 apps mapping a fulslcreen O-R window, but it has its limits.
<ofourdan>
for applications that need to chnage the mode, those which fail the existing heuritics in Xwayland, I'd advise to try Xwayland rootful instead.
<DodoGTA>
ofourdan: Wine's "virtual desktop" mode has its own display mode management (so it works correctly for the particular application I'm using) and rootful mode isn't needed for that so I might have to keep using it
kts has quit [Ping timeout: 480 seconds]
Guest1205 has quit [Remote host closed the connection]
<pq>
maybe wine-wayland driver will work even better once the display mode management gets to upstream Wine
cool110 has joined #wayland
<davidre>
I wonder if XWayland should have clipboard and drag and drop briding ootb instead of compositors having to implement that
cool110 is now known as Guest1343
Company has joined #wayland
Guest1343 has quit [Remote host closed the connection]
<pq>
I guess it could work, but in less cases than with compositor integration.
<pq>
unless nowadays something in either cb or dnd relies of xdg extensions?
<davidre>
I am only slightly traumatized from reading the Xdnd specifications