You need to sign in or sign up before continuing.
Commit 7a2836f8 authored by Ulrich Sibiller's avatar Ulrich Sibiller Committed by Mike Gabriel

Update currentTime in dispatch loop

commit 312910b4e34215aaa50fc0c6092684d5878dc32f Author: Chase Douglas <chase.douglas@canonical.com> Date: Wed Apr 18 11:15:40 2012 -0700 Update currentTime in dispatch loop A request, like input device grabs, may check a request timestamp against currentTime. It is possible for currentTime to lag a previously sent event timestamp. If the client makes a request based on such an event timestamp, the request may fail the validity check against currentTime unless we always update the time before processing the request. Signed-off-by: 's avatarChase Douglas <chase.douglas@canonical.com> Reviewed-by: 's avatarPeter Hutterer <peter.hutterer@who-t.net>
parent 2589a134
...@@ -407,6 +407,9 @@ Dispatch(void) ...@@ -407,6 +407,9 @@ Dispatch(void)
} }
/* now, finally, deal with client requests */ /* now, finally, deal with client requests */
/* Update currentTime so request time checks, such as for input
* device grabs, are calculated correctly */
UpdateCurrentTimeIf();
result = ReadRequestFromClient(client); result = ReadRequestFromClient(client);
if (result <= 0) if (result <= 0)
{ {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment