mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1101] Setting hotkeys using GUI doesn't print what works into the config #882
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#882
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JoshQuake on GitHub (Mar 15, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1101
I tried setting a hotkey to duplicate the same key on the client, but when restarting the server it gets stuck on "Barrier is starting."
I simply want to press Numpad + while on server pc and it press Numpad + on the client. Is this not possible?
EDIT: It actually gets stuck when setting a hotkey at all. Tried having it press a different key and still stuck on Barrier is starting.
@JoshQuake commented on GitHub (Mar 15, 2021):
Here's the error in the log:
[2021-03-14T20:34:19] ERROR: cannot read configuration "C:/Users/jwake/AppData/Local/Temp/Barrier.YAEuXI": read error: line 38: unable to parse key modifiers
barriers.exe: no configuration available
I guess numpad+ isn't compatible.
@JoshQuake commented on GitHub (Mar 15, 2021):
Saved config to PC and set Barrier to use that specific file. Manually edited the config and changed "+" to "KP_Add" and it now works. So setting hotkeys using GUI doesn't print what works into the config.
@p12tic commented on GitHub (Jun 25, 2021):
Thanks for reporting this bug, I'm reopening this issue as we certainly should fix it.