Keystroke flow in X.org
peter.hutterer at who-t.net
Sun Jun 14 16:33:03 PDT 2009
On Mon, Jun 15, 2009 at 09:05:57AM +1000, Peter Hutterer wrote:
> > Here's the link again:
> > http://computerstuff.jdarx.info/content/keystroke-flow-xorg
> I still think it's confusing at best. The diagram makes it appear as if the
> files were actually used on each keystroke, which certainly isn't the case.
> The keys symbols only matter if the keysym describes a "compat" (i.e.
> action) or a modifier, otherwise the server just passes it on. If it's a
> compat or modifier, the server actually processes something based on the
> once the keycode hits the server it doesn't change anymore, so the scancode
> to keycode translation (in evdev that's essentially 'kernel keycode + 8') is
> done in the driver only.
> the keycode to keysym translation is done in the client (with the
> compat/modifier exception above).
> all files in xkb/* are actually aimed for RMLVO configuration, not for
> direct work with the Kcgst. see also
> unfortunately, key processing is more complex than it possibly should be, so
> any attempt to squash it into a small article will miss out vital bits
> important for understanding the overall concept.
doh. either you just changed the graphics in the last 10 minutes or I was
looking at the cached version before. sorry.
the current diagram is much better, thanks.
More information about the xorg