mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1059] Creating a "held down key" hotkey does not work #843
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#843
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 @Azzurite on GitHub (Feb 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1059
Describe the bug
I created a hotkey like this:
I would expect that when I press down
1, it sends a keyDown2event to all screens, and when I release1, that it sends a keyUp2event to all screens. In a text editor for example, I would expect that I could hold down1and a lot of2s would start appearing as long as I hold down the1key. Instead, however, only a single2is sent and it doesn't look like the key is held at all.I used a browser to visualize this by running this script:
it makes the browser window red when the key is held, and shows how often a new keypress is detected. What happens right now is that when I press down
1, the window goes red and shows 1 keypress, and the counter stays at 1. When I release1, nothing happens, the window stays red.If I use a physical key (not a hotkey) to do the same, when I press down
2, the window goes red and the counter starts counting up as long as I hold the key. When I release the2key, the counter stops incrementing and the window goes white.Expected behavior
I would expect both the physical key behavior as well as the hotkey behavior when configured like this to be the same.
To Reproduce
122Desktop (please complete the following information):