nanogui: Re: Generic Input Event question
Subject:
Re: [nanogui] Generic Input Event question
From:
"Greg Haerr" ####@####.####
Date:
10 Jun 2008 23:27:56 -0000
Message-Id: <013901c8cb51$d86e5cc0$6401a8c0@winXP>
> Could I assume no one has ever lost an input events (once it is delivered
> by the driver) regardless of the input driver (i.e just me)?.
There are three distinct layers for mouse events. They start
with the driver, which directly interfaces with the kernel,
using either a select (preferred), or polling interface with
the nano-X main loop. These are in drivers/mou*.c.
The event is then passed to the engine layer, which
handles system wide transformations (all the transforms
and filters should be in this layer, but aren't due to hacking).
The engine layer determines whether which "event" is to
be generated (for either win32 or nano-X APIs), and
will sometimes add information (like which buttons where down
during mouse move, etc). This is engine/devmouse.c.
The upper API layer is then called which handles
API system-specific activities for the event (in nano-X
this is usually nanox/srvevent.c and nanox/srvutil.c).
So there can be many areas to look when talking about
"dropped" events.
Regards,
Greg
