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
carbonfiber has quit [Quit: Connection closed for inactivity]
Leopold has quit [Remote host closed the connection]
Serus has joined #wayland
Leopold_ has joined #wayland
sav10 has quit [Remote host closed the connection]
columbarius has joined #wayland
lbia has joined #wayland
lbia has quit []
co1umbarius has quit [Ping timeout: 480 seconds]
lbia has joined #wayland
wroathe has joined #wayland
Leopold_ has quit [Remote host closed the connection]
bencrus[m] has quit [autokilled: Possible spambot. Mail support@oftc.net if you think this is in error. (2022-10-18 01:45:13)]
wroathe has quit [Ping timeout: 480 seconds]
gabban has joined #wayland
zebrag has quit [Read error: Connection reset by peer]
andyrtr_ has joined #wayland
andyrtr has quit [Read error: Connection reset by peer]
andyrtr_ is now known as andyrtr
<gabban>
Hello all so I'm on Debian SID, and I have two Logitech M650 Mice (right-handed and left-handed). Listed as event17 and event18 respectively. I am trying to set the left-handed mouse property to swap the primary and secondary clicks (event17). I posted in other debian channels but they referred me here. Here's the example output https://pastebin.com/cwhKJGu5 ... Anyone have any helpful ideas or direction?
<gabban>
:-D
nerdopolis has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
<tleydxdy>
interesting, I would totally think those mouse would have the buttons already swapped in firmware
<gabban>
that's what i thought
<gabban>
so i'm trying something with "solaar" and using the right mouse with bluetooth... and the left mouse with the receiver now... i'm trying to figure how to swap the buttons in that "solaar" app... this is driving me nuts
<gabban>
i've got dconf editor open too trying to differentiate the mice but they show up as the same :/ i'm so confused this shouldnt be so hard :(
<soreau>
what compositor are you using?
<gabban>
i'm a little noob/fresh here... compositor?
<gabban>
ah yes i'm on gnome... i'm running the SID repo... so when I try to do X11/Xorg stuff it keeps giving me the wayland warning
<gabban>
(11 - bullseye)
<tleydxdy>
and seem like there's an lefthanded option for the logitech mouse ib that terminal
<gabban>
what command would i use to enable that property in the CLI?
<tleydxdy>
no idea how gnome would do it
<gabban>
ok thanks for the help, if anyone knows please lmk
<gabban>
here's the setup i'm trying now. i connected both via bluetooth (not USB receiver) i'm giving up on "Solaar". In my devices (Left = event17) and (Right = event18) when I do "libinput list-devices" so it looks like https://snipboard.io/AS564n.jpg
<gabban>
as in, it turns on the debugger, but it doesn't swap the mouse buttons is there a way to just "enable left handed" ? like without monitoring those debugging events? sorry if i sound like newbie (because i am)
<tleydxdy>
yeah read the whole thing, not like me and just grep for some keywords xd
<gabban>
oh wait... so in the debug mode... when i use the --enable-left-handed flag... the right click IS inverted as BTN_LEFT and the left click IS inverted as BTN_RIGHT... but the primary click is still poppin up things like the context menu
<tleydxdy>
how weird
<tleydxdy>
is there even an global left handed setting for gnome?
<tleydxdy>
one that applies to all mouse
<gabban>
yes there is ... but i still wanna maintain my right mouse
<tleydxdy>
yeah just wondering if it's something they didn't even think about
<tleydxdy>
i guess not
<gabban>
yeah thanks for your help tho man... you got me pretty close... gave some good insight.
<tleydxdy>
np, good luck
<gabban>
i'm gonna go try again with "Solaar" maybe i can do like button remap there.
tzimmermann has joined #wayland
gabban1 has joined #wayland
gabban has quit [Read error: Connection reset by peer]
zidbon has joined #wayland
cvmn has joined #wayland
gabban has joined #wayland
gabban1 has quit [Read error: Connection reset by peer]
zidbon has quit []
caveman_ has joined #wayland
caveman__ has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
cvmn has quit [Ping timeout: 480 seconds]
hardening has joined #wayland
jgrulich has joined #wayland
caveman_ has quit [Ping timeout: 480 seconds]
ofourdan has joined #wayland
cool110 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
cool110 has joined #wayland
dcz_ has joined #wayland
manuel_ has joined #wayland
mvlad has joined #wayland
rasterman has joined #wayland
Company has joined #wayland
manuel_ has quit [Ping timeout: 480 seconds]
danvet has joined #wayland
manuel_ has joined #wayland
gschwind has joined #wayland
MajorBiscuit has joined #wayland
fahien has joined #wayland
lbia1 has joined #wayland
lbia has quit [Ping timeout: 480 seconds]
<pq>
kennylevinsen, popups sometimes wants grabs, so maybe the destroy order is defined to make it clear which remaining popup gets the grab next?
<pq>
gabban, tleydxdy, you cannot use libinput cli tools to change what input device configuration a desktop uses.
<pq>
there is no way for the libinput cli tool to tell the desktop to do something, by design
<pq>
gabban, you'd really need GNOME to support our use case explicitly by somehow offering per-device (rather than per-pointer or global) mouse settings.
<kennylevinsen>
pq: If grabs should just go to the next in the stack too, then destroying out of order shouldn't matter too much. "Next in stack" is still valid...
<pq>
next in which direction?
<pq>
oh right, middle one cannot have grab
<pq>
what about positioning? aren't each positioned relative to its parent?
<kennylevinsen>
Yeah, within popups of popups it wouldn't make much sense to kill the middle popup. Would need a way to reparent.
<kennylevinsen>
but it wouldn't be unreasonable to have multiple popups off the same toplevel
<pq>
if you have multiple wl_seats, sure...
<pq>
one per wl_seat
<pq>
but it's difficult to imagine what the UX would be with multiple popup stacks on the same seat
<kennylevinsen>
or tablet/touch/mouse, or temporary notification thingie + context menu
<pq>
hmm, ok
<pq>
maybe just lack of imagination in design phase?
<jadahl>
notification thingie + context menu should be possible already
<kennylevinsen>
if a notification popup is created after a context menu popup off the same toplevel, it becomes a protocol error to destroy the context menu before the notification
<kennylevinsen>
at least by the spec
<jadahl>
kennylevinsen: isn't that order thing only specifiet to be relevant for grabbing popups?
<jadahl>
that might be something left from the time before grab() was introduced
<kennylevinsen>
could be, don't know much about the history there
<jadahl>
e.g. if I open a menu, and start triggering tooltips here and there outside of that menu, those tooltips can show/hide/show/hide despite them not being the "single" top most popup
<jadahl>
in some older version of xdg-shell, there was no grab() and all popups always grabbed
<jadahl>
but that made tooltips impossible to implement, so the grabbing (a.k.a. autohide/autodismissed) optional
<jadahl>
*was made
<kennylevinsen>
ah, yeah that does sound very inflexible