[GH-ISSUE #657] Suggestion: provide visual feedback in main barrier window if scroll lock is on (cursor locked to screen) #517

Open
opened 2026-05-05 06:34:55 -06:00 by gitea-mirror · 10 comments
Owner

Originally created by @XertroV on GitHub (May 7, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/657

Spent a good 10 minutes trying to figure out why things weren't working (after a slightly rocky getting connected dance). The ONLY feedback given to the user to indicate scroll lock will lock the cursor to the screen is ONE LINE IN THE LOG, which I only noticed because I had the log open from the connection troubles.

There is nothing in any of the 3 tabs of 'configure server' (two of which are 'hotkeys' and 'advanced'). TBH I'd say at this stage it's more important not to ruin someone's experience than to have a silent scroll-lock feature. But the better soln is just to put a status msg somewhere.

Barrier is great -- now. It would have been a shame if I'd given up a few min earlier just because there wasn't little red msg on the server status page.

Originally created by @XertroV on GitHub (May 7, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/657 Spent a good 10 minutes trying to figure out why things weren't working (after a slightly rocky getting connected dance). The **ONLY** feedback given to the user to indicate scroll lock will lock the cursor to the screen is **ONE LINE IN THE LOG**, which I only noticed because I had the log open from the connection troubles. There is nothing in any of the 3 tabs of 'configure server' (two of which are 'hotkeys' and 'advanced'). TBH I'd say at this stage it's more important not to ruin someone's experience than to have a silent scroll-lock feature. But the better soln is just to put a status msg somewhere. Barrier is great -- now. It would have been a shame if I'd given up a few min earlier just because there wasn't little red msg on the server status page.
gitea-mirror added the
bug
enhancement
help wanted
labels 2026-05-05 06:34:55 -06:00
Author
Owner

@wrgrant commented on GitHub (Sep 19, 2020):

Yes. This is bad UX. Hidden features = frustrating.

Just disable the hard coded ScrollLock binding.

If someone wants to enable this feature they can setup a hotkey.

<!-- gh-comment-id:695368027 --> @wrgrant commented on GitHub (Sep 19, 2020): Yes. This is bad UX. Hidden features = frustrating. Just disable the hard coded ScrollLock binding. If someone wants to enable this feature they can setup a hotkey.
Author
Owner

@bsdfirst commented on GitHub (Oct 23, 2020):

After a bunch of frustration and the subsequent discovery of the same "ONE LINE IN THE LOG", I was about to go read the source code when I found this. Scroll-lock. Sigh.

<!-- gh-comment-id:714858359 --> @bsdfirst commented on GitHub (Oct 23, 2020): After a bunch of frustration and the subsequent discovery of the same "ONE LINE IN THE LOG", I was about to go read the source code when I found this. Scroll-lock. Sigh.
Author
Owner

@hrafnkelle commented on GitHub (Nov 6, 2020):

Glad I found this thread. I was going mad. Had to enable DEBUG1 to see "locked to screen" and could then find this. Please make this more visible.

<!-- gh-comment-id:722994012 --> @hrafnkelle commented on GitHub (Nov 6, 2020): Glad I found this thread. I was going mad. Had to enable DEBUG1 to see "locked to screen" and could then find this. Please make this more visible.
Author
Owner

@sargon2 commented on GitHub (Jan 26, 2021):

+1. I just ran into this. Very frustrating trying to figure out why Barrier is not working when it should be. I even checked "hotkeys" to see if I had a hotkey set up that might be breaking it, and the list was empty.

<!-- gh-comment-id:767655597 --> @sargon2 commented on GitHub (Jan 26, 2021): +1. I just ran into this. Very frustrating trying to figure out why Barrier is not working when it should be. I even checked "hotkeys" to see if I had a hotkey set up that might be breaking it, and the list was empty.
Author
Owner

@dnunes commented on GitHub (Mar 1, 2021):

I also had this problem for a while before taking the time to check the logs in Debug 2 mode, but even then the "Locked to screen" is not very helpful because it doesn't say why. I had to do a Google Search to get here and find out the ScrollLock was the culprit. I don't even know how to toggle my ScrollLock on my computer as I don't have that key anymore for years now, so I had to go into the On-screen Keyboard to deactivate it.

Please just disable this behavior or add some information about it somewhere (a visual indicator on the main screen would be enough). At the absolute very minimum, change the log message to "Locked to Screen because ScrollLock is active" or something and maybe move it to "Debug" level.

<!-- gh-comment-id:788142208 --> @dnunes commented on GitHub (Mar 1, 2021): I also had this problem for a while before taking the time to check the logs in Debug 2 mode, but even then the "Locked to screen" is not very helpful because it doesn't say why. I had to do a Google Search to get here and find out the ScrollLock was the culprit. I don't even know how to toggle my ScrollLock on my computer as I don't have that key anymore for years now, so I had to go into the On-screen Keyboard to deactivate it. Please just disable this behavior or add some information about it somewhere (a visual indicator on the main screen would be enough). At the absolute very minimum, change the log message to "Locked to Screen because ScrollLock is active" or something and maybe move it to "Debug" level.
Author
Owner

@breakingspell commented on GitHub (Mar 1, 2021):

Agreed that this behavior should be reworked. I use Scroll Lock as a toggle for AHK scripts, it made Barrier seem unreliable when it was operating as designed.
To confirm, setting another hotkey for lockCursorToScreen (Alt+Shift+Scroll Lock in my case) takes the binding off of Scroll Lock by itself, but some kind of indicator for the cursor lock (OSD, systray) would be superb.

<!-- gh-comment-id:788177775 --> @breakingspell commented on GitHub (Mar 1, 2021): Agreed that this behavior should be reworked. I use Scroll Lock as a toggle for AHK scripts, it made Barrier seem unreliable when it was operating as designed. To confirm, setting another hotkey for lockCursorToScreen (Alt+Shift+Scroll Lock in my case) takes the binding off of Scroll Lock by itself, but some kind of indicator for the cursor lock (OSD, systray) would be superb.
Author
Owner

@stevleibelt commented on GitHub (Jun 23, 2021):

Thank you very much @XertroV for this post.
As 100 percent of the others, I came here by browsing the issue list searching for "locked to screen".

I must admit, I am not using the "scroll lock" (in german "Rollen") key at all. That's why it took me so long to figure out this key was pressed (by mistake).

<!-- gh-comment-id:866595092 --> @stevleibelt commented on GitHub (Jun 23, 2021): Thank you very much @XertroV for this post. As 100 percent of the others, I came here by browsing the issue list searching for "locked to screen". I must admit, I am not using the "scroll lock" (in german "Rollen") key at all. That's why it took me so long to figure out this key was pressed (by mistake).
Author
Owner

@p12tic commented on GitHub (Jun 25, 2021):

I would say that this behavior is so confusing that it makes sense to call it a bug.

<!-- gh-comment-id:868521297 --> @p12tic commented on GitHub (Jun 25, 2021): I would say that this behavior is so confusing that it makes sense to call it a bug.
Author
Owner

@coolspot18 commented on GitHub (Feb 9, 2022):

What do do if scroll lock is actually needed like in Microsoft Excel?

<!-- gh-comment-id:1034199967 --> @coolspot18 commented on GitHub (Feb 9, 2022): What do do if scroll lock is actually needed like in Microsoft Excel?
Author
Owner

@mirh commented on GitHub (Feb 25, 2022):

Then you are probably interested to #1252 or #435
This bug instead is a duplicate of #482

<!-- gh-comment-id:1051261110 --> @mirh commented on GitHub (Feb 25, 2022): Then you are probably interested to #1252 or #435 This bug instead is a duplicate of #482
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#517
No description provided.