[GH-ISSUE #260] Feature: Add a keyboard shortcut to change to different screens #130

New issue

Open

opened 2026-05-05 22:10:48 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 22:10:48 -06:00

Owner

Originally created by @markmandel on GitHub (Feb 8, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/260

Reading around, there are requests for this buried in other requests (https://github.com/feschber/lan-mouse/issues/26#issuecomment-1832877166, https://github.com/feschber/lan-mouse/issues/139#issuecomment-2147995949) - but since I would really like this feature, I'm pulling it out into it's own issue so it doesn't get lost.

Basically, i want what Synergy does (and input-leap, etc): https://symless.com/synergy/help/add-a-hotkey-or-keyboard-shortcut-to-change-to-different-screens

Basically because I tend to do most navigation by keyboard, so switching to mouse just to move my mouse up the page to switch screens is cumbersome for me. Would be great to be able to press my own custom key combo, and have it switch to a different monitor.

Originally created by @markmandel on GitHub (Feb 8, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/260 Reading around, there are requests for this buried in other requests (https://github.com/feschber/lan-mouse/issues/26#issuecomment-1832877166, https://github.com/feschber/lan-mouse/issues/139#issuecomment-2147995949) - but since I would really like this feature, I'm pulling it out into it's own issue so it doesn't get lost. Basically, i want what Synergy does (and input-leap, etc): https://symless.com/synergy/help/add-a-hotkey-or-keyboard-shortcut-to-change-to-different-screens Basically because I tend to do most navigation by keyboard, so switching to mouse just to move my mouse up the page to switch screens is cumbersome for me. Would be great to be able to press my own custom key combo, and have it switch to a different monitor.

gitea-mirror commented

2026-05-05 22:10:51 -06:00

Author

Owner

@markmandel commented on GitHub (Feb 8, 2025):

Fun workaround I figured I'd share! I'm using hyprland, but this just requires a keybinding and wlctrl.'

bind = CTRL ALT, Up, exec, wlrctl pointer move 0 -10000
bind = CTRL ALT, Down, exec, wlrctl pointer move 0 10000

Since the edge transition fires when the mouse goes to the edge, you can move it there with wlrctl.

It's not perfect, since your mouse is now at the top of your screen - but if you are using keyboard navigation anyway, it may not matter much to you.

@markmandel commented on GitHub (Feb 8, 2025): Fun workaround I figured I'd share! I'm using hyprland, but this just requires a keybinding and `wlctrl`.' ``` bind = CTRL ALT, Up, exec, wlrctl pointer move 0 -10000 bind = CTRL ALT, Down, exec, wlrctl pointer move 0 10000 ``` Since the edge transition fires when the mouse goes to the edge, you can move it there with wlrctl. It's not perfect, since your mouse is now at the top of your screen - but if you are using keyboard navigation anyway, it may not matter much to you.

gitea-mirror commented

2026-05-05 22:10:52 -06:00

Author

Owner

@feschber commented on GitHub (Feb 12, 2025):

Yeah, this is something I definitely want to do at some point. The input capture portal currently does not allow for this directly so it would have to be a hack similar to what you are describing above (though it would hopefully work better when integrated with lan-mouse directly).

@feschber commented on GitHub (Feb 12, 2025): Yeah, this is something I definitely want to do at some point. The input capture portal currently does not allow for this directly so it would have to be a hack similar to what you are describing above (though it would hopefully work better when integrated with lan-mouse directly).

gitea-mirror commented

2026-05-05 22:10:53 -06:00

Author

Owner

@rpatterson commented on GitHub (Jan 10, 2026):

It's not perfect, since your mouse is now at the top of your screen - but if you are using keyboard navigation anyway, it may not matter much to you.

Clever workaround! But just to represent another use case, I used keyboard shortcuts/hotkeys mostly so I could not use screen edges at all. Over many years of Synergy -> Barrier -> Input-leap usage, the frequency of accidental screen changes has always been a bad UX for me. There are good reasons to want to "throw" the mouse to each of the 4 edges as a way to get to a UI element quickly: menus, docks, scroll bars, modals, top/bottom/left/right edge of a "page", etc.. So overloading the screen edges is always going to clash with user intention a significant proportion of times.

@rpatterson commented on GitHub (Jan 10, 2026): > It's not perfect, since your mouse is now at the top of your screen - but if you are using keyboard navigation anyway, it may not matter much to you. Clever workaround! But just to represent another use case, I used keyboard shortcuts/hotkeys mostly so I could not use screen edges at all. Over many years of Synergy -> Barrier -> Input-leap usage, the frequency of accidental screen changes has always been a bad UX for me. There are good reasons to want to "throw" the mouse to each of the 4 edges as a way to get to a UI element quickly: menus, docks, scroll bars, modals, top/bottom/left/right edge of a "page", etc.. So overloading the screen edges is always going to clash with user intention a significant proportion of times.