mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-16 05:30:28 +00:00
f9df0fc94c
Some drivers don't do that (not sure whether that is the correct behaviour or not). Remember each WT_PROXIMITY with LOWORD(lParam) != 0 that we get, then look for a WT_CSRCHANGE. If WT_CSRCHANGE doesn't come, but a WT_PACKET does, assume that this device is the one that sent WT_PROXIMITY. Also include fallback code to ensure that WT_PACKETs for an enabled device disable the system pointer, because WT_PROXIMITY handler might have enabled it by mistake, since it's not possible to know which device left the proximity (it might have been a disabled device). https://bugzilla.gnome.org/show_bug.cgi?id=778328 |
||
|---|---|---|
| .. | ||
| rc | ||
| bdfcursor.c | ||
| cursor.bdf | ||
| gdkcursor-win32.c | ||
| gdkdevice-virtual.c | ||
| gdkdevice-virtual.h | ||
| gdkdevice-win32.c | ||
| gdkdevice-win32.h | ||
| gdkdevice-wintab.c | ||
| gdkdevice-wintab.h | ||
| gdkdevicemanager-win32.c | ||
| gdkdevicemanager-win32.h | ||
| gdkdisplay-win32.c | ||
| gdkdisplay-win32.h | ||
| gdkdisplaymanager-win32.c | ||
| gdkdnd-win32.c | ||
| gdkevents-win32.c | ||
| gdkgeometry-win32.c | ||
| gdkglcontext-win32.c | ||
| gdkglcontext-win32.h | ||
| gdkglobals-win32.c | ||
| gdkkeys-win32.c | ||
| gdkmain-win32.c | ||
| gdkmonitor-win32.c | ||
| gdkmonitor-win32.h | ||
| gdkprivate-win32.h | ||
| gdkproperty-win32.c | ||
| gdkscreen-win32.c | ||
| gdkselection-win32.c | ||
| gdktestutils-win32.c | ||
| gdkwin32.h | ||
| gdkwin32cursor.h | ||
| gdkwin32display.h | ||
| gdkwin32displaymanager.h | ||
| gdkwin32dnd.h | ||
| gdkwin32glcontext.h | ||
| gdkwin32id.c | ||
| gdkwin32keys.h | ||
| gdkwin32misc.h | ||
| gdkwin32monitor.h | ||
| gdkwin32screen.h | ||
| gdkwin32window.h | ||
| gdkwindow-win32.c | ||
| gdkwindow-win32.h | ||
| libwntab32x.la | ||
| Makefile.am | ||
| makefile.msc | ||
| pktdef.h | ||
| wintab.h | ||
| xcursors.h | ||