[GH-ISSUE #635] [Feature request] - sync select keyboard shortcuts between client/server #504

New issue

Open

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

gitea-mirror commented

2026-05-05 06:33:10 -06:00

Owner

Originally created by @Onepamopa on GitHub (Apr 23, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/635

For example - sync [Alt] [Shift] to [Alt] [Shift] between sever <-> client.
Could also be configurable shortcuts on both sides.

This is mostly to sync the keyboard layout changes between them, hoping that'd fix a nasty bug, but could obviously be used for a lot of things.

Right now if the active window is set to "BG" and move the cursor to the client, I wont be able to type anything, or change the layout.. I have to go back to the server, change the active window to "EN" then move back to the client and use it. Local layout changes on the client don't fix the issue (i.e. I manually switch to "BG" then back to "EN" - I'm still not able to type anything).

Server: Windows 10 (with "Let me use a different input method for each app window" enabled)
Client: FreeBSD 12.1
Haven't tested with other clients yet.

If there is a quick fix for this, let me know :)

Originally created by @Onepamopa on GitHub (Apr 23, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/635 For example - sync [Alt] [Shift] to [Alt] [Shift] between sever <-> client. Could also be configurable shortcuts on both sides. This is mostly to sync the keyboard layout changes between them, hoping that'd fix a nasty bug, but could obviously be used for a lot of things. Right now if the active window is set to "BG" and move the cursor to the client, I wont be able to type anything, or change the layout.. I have to go back to the server, change the active window to "EN" then move back to the client and use it. Local layout changes on the client don't fix the issue (i.e. I manually switch to "BG" then back to "EN" - I'm still not able to type anything). Server: Windows 10 (with "Let me use a different input method for each app window" enabled) Client: FreeBSD 12.1 Haven't tested with other clients yet. If there is a quick fix for this, let me know :)

gitea-mirror commented

2026-05-05 06:33:14 -06:00

Author

Owner

@pklapperich commented on GitHub (May 1, 2020):

I'm not sure I understand this request. Keyboard shortcuts typed on the server should already flow to the client. It sounds like your issue is related to input language, not keyboard shortcuts.

The setting "Let me use a different input method for each app window" on Windows 10 is a bit of a hack in that it swaps the keyboard driver's button map as you switch between windows. Since Barrier monitors the keyboard regardless of the active window, I believe Barrier receives keyboard input based on whatever input method was last selected on Windows.

I think the best way to address this would probably be for Barrier switch the language back to the Windows default language whenever the mouse moves off the server. From brief research it looks like this might be possible, but I'm not 100% sure.

@pklapperich commented on GitHub (May 1, 2020): I'm not sure I understand this request. Keyboard shortcuts typed on the server should already flow to the client. It sounds like your issue is related to input language, not keyboard shortcuts. The setting "Let me use a different input method for each app window" on Windows 10 is a bit of a hack in that it swaps the keyboard driver's button map as you switch between windows. Since Barrier monitors the keyboard regardless of the active window, I believe Barrier receives keyboard input based on whatever input method was last selected on Windows. I think the best way to address this would probably be for Barrier switch the language back to the Windows default language whenever the mouse moves off the server. From brief research it looks like this might be possible, but I'm not 100% sure.

gitea-mirror commented

2026-05-05 06:33:16 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 23, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:33:18 -06:00

Author

Owner

@ageorgios commented on GitHub (Oct 30, 2020):

I have the same problem, keyboard layouts do not sync

@ageorgios commented on GitHub (Oct 30, 2020): I have the same problem, keyboard layouts do not sync