Barrier: Pointer disappearing - HiDPI related?

[Mibo5354]

Operating Systems

Server: Windows 10 1809 - 1920x1080 with 125% scaling

Client: Manjaro Linux - 1366x786

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

1. Turn on Barrier and connect the machines
2. On server
3. Move mouse around and try to move to the other machine
4. Pointer disappears and does not reappear
5. Disconnect from the client machine to restore pointer

Other info

• When did the problem start to occur? Since I set it up
• Is there a way to work around it? No, I tried tweaking the hidpi setting for barriers.exe but nothing worked. HiDPI settings has changed from 1709 hence workaround listed in #42 is not applicable. On a side note, is there binaries for 2.2 mentioned in the other issue so I can see if it is fixed?
• Does this bug prevent you from using Barrier entirely? Yes

There seem to be a window of movement on the server machine that is equal to the resolution of the client. The window starts from the top left corner and I can move the pointer without it disappearing but when it moves out it disappears until I disconnect.
This occurs on synergy [1.4.12] as well, that's why I tried out barrier.

[pgetsos]

Have the same issue, workaround didn't work as well

[tungmeister]

I've got the same issue, my mouse will disappear after moving ~75% over my main monitor and it's practically impossible to get it to appear again.

[noisyshape]

I suspect this is the same issue as #206, #194, and #94. The problem is resolved for me with a 2.2.0 build.

[Mibo5354]

@noisyshape is there binaries for a 2.2.0 build?

[noisyshape]

@Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

[Mibo5354]

@noisyshape is the instructions on the wiki still good, or is there any changes I should know about?

[noisyshape]

@Mibo5354 The instructions are good. Just follow them carefully. Once you have the binaries, stop all Barrier processes and copy everything into your existing installation folder. If you can't complete the build, start a new issue and I'll try to help.

Edit: There is one problem that I know of. Qt doesn't support VS2019 yet, so you'll need VS2017 to follow the build guide. If you use VS2019, you'll have to use the VS2017 Qt libraries and edit the clean_build.bat string Visual Studio 15 2017 Win64 to Visual Studio 16 2019. The resulting build seems to be fine.

[sommoMicc]

@Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

Plz can you upload somewhere (like in google drive) the 2.2.0 Windows build?

[Mibo5354]

@sommoMicc Here's the build that I compiled today https://drive.google.com/file/d/1S3Z5mLQT63ZTWIsjiTyzL9qdIjoE-MW1/view?usp=sharing

[AdrianKoshka]

@Mibo5354 No there aren't. It looks like there are some problems with the Windows build system. The binaries compile fine though and I can email you a zip file if you're desperate enough.

Plz can you upload somewhere (like in google drive) the 2.2.0 Windows build?

This should be happening soon-ish™¹? Waiting for a PR to fix something with the windows installer script. Then I'll be able to make a build and official release.

1. Soon means probably within the next week, going on a vacation, and most likely won't be bringing my laptop with me.

[Mibo5354]

The issue is solved with the newer build, should I close this issue?

[sommoMicc]

The issue is solved with the newer build, should I close this issue?

Yes. Now it works