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.
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.
Most helpful comment
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.