mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1252] Optional screen-locking with Scroll Lock on #1009
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#1009
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 @TheYuriG on GitHub (Aug 19, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1252
Hello!
This is not exactly an issue, but a request.
I have one of those LED colored keyboards and the lights turn on and off based off scroll lock status. This means i need to consistently turn off the lights to change the screens and then turn on again to be able to see my keyboard (First World problems, i know).
Could it possibly be added an option in the settings to ignore Scroll Lock status and always change screens? Make it enabled by default and disabled by choice, so it's not a breaking change or different behavior for new users.
Thank you!
@echo-bravo-yahoo commented on GitHub (Dec 1, 2021):
+1. I'm having some issues because none of my keyboards (a laptop keyboard, a standard 60%, and a custom QMK with an unusual layout) have a scroll lock button, and for some reason, my Ubuntu laptop appears to have scroll lock ON. I'll probably dig another keyboard out of the closet to turn scroll lock off on my laptop and hope it's not set ON during boot, but it's a big hassle (and not a feature I plan on using, since it's bound to a key I can't press!..)
EDIT: Turns out the issue was (some combination of) Barrier@2.4.0 on Windows 10 as a server, and/or Wayland on the Linux box. I've changed both (downgrade to 2.3.3 on server, disabled Wayland on the laptop), and it's now working.