mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 22:01:23 -06:00
[GH-ISSUE #659] Immune keys seem to not work #520
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#520
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 @tehbiga on GitHub (May 7, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/659
Operating Systems
Server: Windows 10 1809 (17763.1098)
Client: macOS Mojave 10.14.1
Barrier Version
2.3.2
Steps to reproduce bug
ImmuneKeys.txtas described in wikiFilename and path:
ImmuneKeys.txtplaced in%USERPROFILE%\AppData\Local\BarrierContents:
Log of key in use: (verifying I have the vk value correct and that it is seen by the hook)
Other info
Administrator mode on host applications does not seem to work. I tried to change the elevation option and that didn't help either.
Just downloaded this today because I was sick of swapping cables on my two machines for work.
Everything works great except immune keys which was the key feature I wanted to keep using Discord on my host machine.
I use right-control or F17 as push-to-talk since I have a macro button on my mouse. Even the more standard keys do not seem to work.
@isycat commented on GitHub (Jun 4, 2020):
Struggling with this as well. Exact same story, bunch of different keys attempted.
@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.
@isycat commented on GitHub (Sep 26, 2020):
This is still an issue
@kiraacorsac commented on GitHub (Oct 22, 2020):
This is very much an issue on my side too.
@kiraacorsac commented on GitHub (Oct 22, 2020):
OK, I have a workaround, if this is still an issue for @isycat @tehbiga.
I noticed that in the log, it looks for the ImmuneKeys in the completely wrong directory. I've created the directory that was dumped in the log, and it works as expected. So if you don't mind creating this folder on your computer (requires admin privs), you can enjoy your push to talk (or, in my case, all the media keys) on the correct side of the Barrier. There should be another workaround with running/installing barrier as a correct user, but I can't be bothered.
This actually looks like a fairly easy fix in the DataDirectories.cpp, but I don't want to touch C++ with an eleven-foot pole (and you guys would not want me to touch it either).