12:06 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?
12:07 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?
12:14 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
12:50 zamundaaa[m]: Colin Marc: apps scaling inputs like that would be very confusing
12:50 zamundaaa[m]: The amount you scroll should never depend on the window size
13:58 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
13:58 dviola: I thought that following looked really odd: Input device: "Logitech USB Keyboard Type: Mouse"
13:59 dviola: s/that/the/
14:00 dviola: already tested different compositors, different games, the result is always the same
14:02 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
14:11 dviola: already attached a different keyboard and a "Type: Mouse" appears as well
14:38 dviola: here's what `libinput list-devices` reports: http://0x0.st/XdoK.txt
14:38 dviola: there are two keyboard entries, one as keyboard and the other as pointer, makes no sense
15:14 dviola: looks like libinput maintains a bunch of quirks for mice and keyboard
15:25 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
15:26 dviola: `libinput list-devices` should return a list
15:40 dviola: https://gitlab.freedesktop.org/libinput/libinput/-/issues/986
15:45 dviola: "Mice have ability to send keystroke as hotkey capability"
15:55 dviola: Steam is the only app as far as I am aware that is causing these issues, so I will just give it some time I guess
16:17 dviola: looks like a Steam bug: https://github.com/ValveSoftware/steam-for-linux/issues/11423