From 70fe2325b1be6a7ad4c30b65fd3c0d1a6f620ae1 Mon Sep 17 00:00:00 2001
From: Simon Rettberg
Date: Tue, 30 Jul 2019 15:52:11 +0200
Subject: Flush X events before locking if we have an external ungrab command

The external ungrab command might have generated some synthetic
keyboard or mouse events, which would in turn immediately
disable the screen saver again if it gets activated (but not locked).
This is supposed to help mitigate that case.
---
 driver/windows.c | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'driver/windows.c')

diff --git a/driver/windows.c b/driver/windows.c
index c54f15e..ceba8c8 100644
--- a/driver/windows.c
+++ b/driver/windows.c
@@ -337,6 +337,10 @@ grab_keyboard_and_mouse (saver_info *si, Window window, Cursor cursor,
     {
       snprintf (cmd, sizeof(cmd), "%s %s", euc, "post");
       exec_and_wait (si, cmd);
+      if (ret) {
+        /* The external command might have generated some x/input events */
+        flush_events (si);
+      }
     }
   return ret;
 }
-- 
cgit v1.2.3-55-g7522