problems controlling client after sleeping/resuming server, seems to be scrolllock issue

[snuq]

Operating Systems

Server: Windows 8.1

Client: Windows 8.1

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

1. connect server and client
2. sleep server computer
3. wake server computer

Other info

I start up and connect barrier between the two computers and it works great, but when the server computer (my laptop) sleeps then wakes up, I no longer an able to control the client.

the log on the server displays: """
[
2018-07-23T1
3
:45:4
2]
W
ARNING: f
a
il
e
d to register
hotke
y
S
croll
Lock (
id=ef14
mask=0000)
"""
...yeah, its split up exactly like that...

Both computers say they are connected, but I cannot move the mouse off screen. Enabling and disabling scroll lock does not have any effect.
stopping and starting the server does not fix it, i have to go into the configure server settings, click ok, then click apply, THEN i can use the mouse connection again.

[Zackhardtoname]

still having this problem...

[mirh]

stopping and starting the server does not fix it, i have to go into the configure server settings, click ok, then click apply, THEN i can use the mouse connection again.

I can confirm this did the trick for me, after a hour of attempts.
For some reason Scroll Lock is on, locking cursor to screen just didn't seem to want to go away.

https://github.com/debauchee/barrier/blob/v2.4.0/src/lib/platform/MSWindowsKeyState.cpp#L833
https://github.com/debauchee/barrier/blob/v2.4.0/src/lib/platform/MSWindowsScreen.cpp#L1140
I feel like those functions are some disaster waiting to happen
https://stackoverflow.com/questions/66510965/windows-c-getkeystate-caps-lock-detector-does-opposite
https://stackoverflow.com/questions/45719020/winapi-getkeyboardstate-behavior-modified-by-getkeystate-when-application-is-out