[PATCH 4/4] xfree86 implementation of the input-thread

[Simon Thum]

>>From 54c85abcfb9f6a91f8c40dd332a0a5671ada69e2 Mon Sep 17 00:00:00 2001
> From: Tiago Vignatti <vignatti at c3sl.ufpr.br>
> Date: Fri, 5 Sep 2008 15:17:30 +0100
> Subject: [PATCH 4/4] xfree86 implementation of the input-thread.
> 
> he urgently TODO here is to hook into Enable/DisableDevice to start/pause
> thread when devices are removed. Probably a hook into OsBlock/ReleaseSignals
> to get the synchronicity for free is also needed.

Hi Guys,

I reasoned a bit more about that issue, so just FYC, here's what I came 
up with:

OsBlock/Release are used for two related, but different issues: Suppress 
event _enqueueing_ or suppress event _processing_. I think that it makes 
sense to split those two blocking behaviors, since the former may be 
cheaper and more common. Also, in the long run, OsBlockSignals() is 
becoming a very misleading name.

Cheers,

Simon