Replies: 9 comments 1 reply
-
You already don't have to click to a window in order to focus on it, when you mouse hover to a window it already focuses. What do you mean? Also how will you scroll on webpages if you set the scroll to switch window? |
Beta Was this translation helpful? Give feedback.
-
I don't have that enabled because I don't want focus to change while I'm in the middle of typing and the mouse gets moved. You're still stuck on the "why". Let's move on to the "how".
It would change focus to whatever window the cursor is hovering over when the scroll wheel is activated. |
Beta Was this translation helpful? Give feedback.
-
How can the mouse be moved if your hands are on your keyboard?
See https://i3wm.org/docs/userguide.html#mousebindings
Please note that scrolling with the scrollwheel might not work anymore in some programs. |
Beta Was this translation helpful? Give feedback.
-
Because I have kids, a wife, and my mousepad is on a slight incline and it's really not important at all because, as has already been stated, the "why" is unimportant. This is why I put that annoying paragraph in the opening section. I did a bunch of googling before coming here and it seems like the i3 community, for some completely illogical reason, has formed the irrational belief that a TWM setup and a keyboard only setup are both mutually necessary. They're not. A TWM just displays the same information, but in a better format, merely by moving and resizing the windows. A keyboard only setup is merely the means of interacting with the same information/windows/setup, but sans one HID. You can have one without the other. So why speculate on the validity of each individual setup when so many different setups can all be valid? Are only community-approved setups permitted to use i3?
I can confirm that is exactly what happened. It does not pass the button press event along. Just like how pressing and releasing meta/super by itself also eats the input and doesn't pass it along to anything else that might be listening. So meta/super alone can no longer open the DE's main menu. Is there a method for forcing keypress events to be passed through to anything else that's listening? That would solve several problems. |
Beta Was this translation helpful? Give feedback.
-
Kind of the opposite is true.
You are speculating too much. To each his own.
Nothing I know of. If you tell the wm to consume the keypress event, it will. I would recommend to not bind the |
Beta Was this translation helpful? Give feedback.
-
Sorry. I meant mutually necessary.
My point exactly.
So if we tell the WM not to consume the keypress event, then it won't, right? |
Beta Was this translation helpful? Give feedback.
-
Yes, but then you don't have any functionality either. Thus my recommendation to use the modifier key to keep the mouse binding from conflicting with applications. |
Beta Was this translation helpful? Give feedback.
-
Not exactly. If anything, it would have extra functionality since every input is being passed along. But that's only if you make it global, which is not what I'm talking about. It can be a flag instead. For example, if the flag was something like
At most, it could only break functionality with that one binding. Global functionality would remain unchanged. |
Beta Was this translation helpful? Give feedback.
-
I don't know if something like that is possible. I guess @stapelberg or @orestisfl can answer that. |
Beta Was this translation helpful? Give feedback.
-
I've grown used to focusing windows using the mouse wheel. It saves me an extra click of a mouse button, in situations where I can unavoidably only use a mouse. Those extra mouse clicks all add up. The more you click, the faster the little Omron switches wear out in your mouse, and the sooner they'll will need to be replaced. Replacing them requires taking the mouse apart, desoldering the old switches, then soldering in some new ones, and putting it all back together. The mouse wheel itself is better suited to handling clicks, where ever possible, as it is much more durable. So switching focus to a new window on scrolling the mouse wheel correctly redirects some of the work load from the switches to the mouse wheel, which is more beneficial to the user.
There. I have preemptively answered the "why" so now we can better focus on the "how".
I can't seem to find any way of doing this. I've gone through the Docs, the FAQ. and I've done both DuckDuckGo and even google searches, and I've found nothing useful in this regard. Is there no way of implementing this function in i3's current state? If that is the case, can I request this feature be implemented in the future?
Any help would be appreciated. Thank you.
Beta Was this translation helpful? Give feedback.
All reactions