Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional screen-locking with Scroll Lock on #1252

Open
TheYuriG opened this issue Aug 19, 2021 · 1 comment
Open

Optional screen-locking with Scroll Lock on #1252

TheYuriG opened this issue Aug 19, 2021 · 1 comment

Comments

@TheYuriG
Copy link

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
Copy link

echo-bravo-yahoo commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants