Files
gtk3/gdk
Руслан Ижбулатов f9df0fc94c GDK W32: Handle drivers that do not send WT_CSRCHANGE after WT_PROXIMITY
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
2017-02-19 07:12:13 +00:00
..
2016-07-22 23:13:20 -04:00
2017-01-30 03:40:18 -05:00
2016-06-29 15:10:39 +02:00
2016-08-23 21:01:44 +02:00
2016-06-09 17:45:40 +01:00
2016-05-17 14:16:39 -04:00
2015-05-08 13:34:25 -04:00
2016-08-23 21:01:44 +02:00
2016-08-23 21:01:44 +02:00
2016-08-23 21:01:44 +02:00
2016-05-08 15:34:28 +02:00
2016-06-09 17:45:40 +01:00
2016-04-30 21:06:38 -04:00
2014-11-06 12:24:43 +01:00
2016-05-08 15:34:28 +02:00
2016-04-27 23:18:16 -04:00
2016-04-18 11:46:58 -04:00
2014-08-30 00:53:21 -04:00
2015-10-03 22:26:27 -04:00
2014-06-11 21:55:15 -04:00
2016-10-28 06:04:58 +02:00
2016-10-28 06:04:58 +02:00
2013-07-17 17:52:19 -04:00