80486DX2-66/86Box-fork
1
0
Fork 0
Code Issues Pull Requests Activity

TigerVNC pointer needs the same workaround as previously added for another VNC server, (#3103)

Browse Source 
but it's pointer is named differently. In addition, it also publishes a pointer
using the XTEST pointer name already added as a workaround. So, if a TigerVNC pointer
is detected, it should be selected first.
This commit is contained in:
Joakim L. Gilje
2023-02-13 17:33:40 +01:00
committed by GitHub
parent a76e9f9d77
commit 16b9a5d3e0
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/qt/xinput2_mouse.cpp
View File

@@ -81,9 +81,17 @@ xinput2_get_xtest_pointer()
{
/* The XTEST pointer events injected by VNC servers to move the cursor always report
absolute coordinates, despite XTEST declaring relative axes (related: SDL issue 1836).
This looks for the XTEST pointer so that we can assume it's absolute as a workaround. */
This looks for the XTEST pointer so that we can assume it's absolute as a workaround.
TigerVNC publishes both the XTEST pointer and a TigerVNC pointer, but actual
RawMotion events are published using the TigerVNC pointer */
int devs;
XIDeviceInfo *info = XIQueryDevice(disp, XIAllDevices, &devs), *dev;
for (int i = 0; i < devs; i++) {
dev = &info[i];
if ((dev->use == XISlavePointer) && !strcmp(dev->name, "TigerVNC pointer"))
return dev->deviceid;
}
for (int i = 0; i < devs; i++) {
dev = &info[i];
if ((dev->use == XISlavePointer) && !strcmp(dev->name, "Virtual core XTEST pointer"))