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
Suggestion: provide visual feedback in main barrier window if scroll lock is on (cursor locked to screen) #657
Comments
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. |
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. |
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. |
+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. |
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. |
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. |
Thank you very much @XertroV for this post. 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). |
I would say that this behavior is so confusing that it makes sense to call it a bug. |
What do do if scroll lock is actually needed like in Microsoft Excel? |
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.
The text was updated successfully, but these errors were encountered: