ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
rasterman has quit [Quit: Gettin' stinky!]
_rgallaispou has quit [Ping timeout: 480 seconds]
kabaka101 has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
kabaka101 has quit [Ping timeout: 480 seconds]
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
nerdopolis has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
Brainium has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has quit [Remote host closed the connection]
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
_whitelogger_ has joined #wayland
feaneron has quit []
_whitelogger_ has quit [Remote host closed the connection]
kts has quit [Ping timeout: 480 seconds]
_whitelogger_ has joined #wayland
abhimanyu1 has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
garnacho has joined #wayland
rv1sr has quit [Remote host closed the connection]
rv1sr has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
feaneron has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #wayland
iomari891 has joined #wayland
feaneron has quit [Quit: feaneron]
rgallaispou has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
kts has joined #wayland
iomari891 has joined #wayland
soreau has quit [Ping timeout: 480 seconds]
_whitelogger_ has quit [Remote host closed the connection]
soreau has joined #wayland
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
iomari891 has quit [Ping timeout: 480 seconds]
rv1sr has quit []
_whitelogger_ has joined #wayland
rv1sr has joined #wayland
kts has quit [Quit: Leaving]
adamtajti_ has joined #wayland
adamtajti has quit [Read error: Connection reset by peer]
Moprius has joined #wayland
adamtajti_ has quit [Read error: Connection reset by peer]
adamtajti has joined #wayland
Moprius has quit [Quit: bye]
_whitelogger_ has quit [Remote host closed the connection]
kts has joined #wayland
rgallaispou has quit [Quit: WeeChat 4.4.3]
colinmarc has joined #wayland
<colinmarc>
do apps usually scale relative motion vectors by surface size? for example, if an app presents a scrollable view, is the scrolling more sensitive if the window is smaller? what about an fps game that hides the cursor and uses relative mouse motion?
<colinmarc>
the context is that I'm wondering if it's correct to scale relative motion vectors in a remote desktop tool. for example, if the app thinks it's rendering fullscreen remotely, but is only a small window locally, should I scale the relative mouse motion to the fullscreen size?
_whitelogger_ has joined #wayland
kts has quit [Quit: Leaving]
<colinmarc>
at least for relative mouse motion, I think I *have* to scale it, since I have to scale absolute motion, and the relative and absolute motion should track - but scrolling is less obvious to me
adamtajti has quit [Ping timeout: 480 seconds]
chiku is now known as Sid127
alatiera has quit [Read error: Connection reset by peer]
alatiera has joined #wayland
adamtajti has joined #wayland
<zamundaaa[m]>
Colin Marc: apps scaling inputs like that would be very confusing
<zamundaaa[m]>
The amount you scroll should never depend on the window size
lsd|2 has joined #wayland
adamtajti has quit [Read error: Connection reset by peer]
<dviola>
hey folks, just to recap the last conversation from #radeon, posting it here because it's less off-topic: so I've been having an issue on Steam where closing the games unmap the Steam window itself as well, after some testing I thought that my input devices could have something to do with this, `swaymsg -t get_inputs` also report the following: https://0x0.st/Xdit.txt
<dviola>
I thought that following looked really odd: Input device: "Logitech USB Keyboard Type: Mouse"
<dviola>
s/that/the/
<dviola>
already tested different compositors, different games, the result is always the same
<dviola>
I've been getting "uninstall" popups on Steam without doing anything, so I've been thinking that maybe there's an issue with the input devices and Steam is getting confused because of it
fmuellner has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
<dviola>
already attached a different keyboard and a "Type: Mouse" appears as well
<dviola>
there are two keyboard entries, one as keyboard and the other as pointer, makes no sense
fmuellner has quit [Ping timeout: 480 seconds]
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
agd5f_ has quit []
agd5f has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
_whitelogger_ has joined #wayland
_whitelogger_ has quit [Remote host closed the connection]
feaneron has joined #wayland
<dviola>
looks like libinput maintains a bunch of quirks for mice and keyboard
_whitelogger_ has joined #wayland
<dviola>
looks like quirks are being added and one can use `libinput quirks list /dev/input/event3` to get a list of quirks for a specific keyboard, etc
<dviola>
`libinput list-devices` should return a list
feaneron has quit [Read error: Connection reset by peer]