vcxsrv
vcxsrv copied to clipboard
ArcticaProject
Part of the screen is non-functional in multi-monitor setups
This is a weird one. We have seen this on a laptop with a second monitor. The setting is like this:
[ HD monitor ] [ Laptop ]
When started in this configuration, the client connects and the remote system is visible, but if the window is on the laptop screen, mouse clicks don't work.
On the HD monitor side, it looks like the only functional area is the part corresponding to the size of the laptop's screen, starting at the upper left corner. Eg:
+----------------[monitor]-------------------+
| | |
| Working | |
| area | |
| | |
+---------------------+ | +------ [laptop] -----+
| | | |
| | | |
| | | |
| | | |
+--------------------------------------------+ +---------------------+
The part that's marked "working area" is the only place in which clicks are ~~wrong~~ working. So, if the remote desktop's window is dragged to the laptop screen, it doesn't respond to clicks. If it's dragged to the upper left corner of the monitor, it works. If it's left in the middle, then part works and part doesn't.
Here's a video of this behavior: https://www.youtube.com/watch?v=lJYQNAsuLP4
What about the Linux client? Same or different behaviour?
Uli
On Fri, Aug 11, 2017 at 11:53 AM, Vadim Troshchinskiy [email protected] wrote:
This is a weird one. We have seen this on a laptop with a second monitor. The setting is like this:
[ HD monitor ] [ Laptop ]
When started in this configuration, the client connects and the remote system is visible, but if the window is on the laptop screen, mouse clicks don't work.
On the HD monitor side, it looks like the only functional area is the part corresponding to the size of the laptop's screen, starting at the upper right border. Eg:
+----------------[monitor]-------------------+ | | | | Working | | | area | | | | | +---------------------+ | +------ [laptop] -----+ | | | | | | | | | | | | | | | | +--------------------------------------------+ +---------------------+
The part that's marked "working area" is the only place in which clicks are wrong. So, if the remote desktop's window is dragged to the laptop screen, it doesn't respond to clicks. If it's dragged to the upper left corner of the monitor, it works. If it's left in the middle, then part works and part doesn't.
Here's a video of this behavior: https://www.youtube.com/watch?v=lJYQNAsuLP4
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I do all my work on multi-monitor setups on Linux, and so does most of the rest of the company, and it works just fine.
We have also verified that everything starts working correctly if you disconnect the monitor from the latop. Something specifically about multi-monitor setups is going wrong.