xserver/xkb
Peter Hutterer 45fb3a934d xkb: push locked modifier state down to attached slave devices
Whenever the master changes, push the locked modifier state to the attached
slave devices, then update the indicators. This way, when NumLock or CapsLock
are hit on any device, the LED will light up on all devices. Likewise, a new
keyboard attached to a master device will light up with the correct
indicators.

The indicators are handled per-keyboard, depending on the layout, i.e. if one
keyboard has grp_led:num set, the NumLock LED won't light up on that keyboard.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Daniel Stone <daniel@fooishbar.org>
2014-03-11 17:43:34 +10:00
..
Makefile.am
README.compiled
XKBAlloc.c
XKBGAlloc.c
XKBMAlloc.c
XKBMisc.c
XKM_file_format.txt
ddxBeep.c
ddxCtrls.c
ddxKillSrv.c
ddxLEDs.c
ddxLoad.c
ddxPrivate.c
ddxVT.c
maprules.c
xkb.c
xkb.h
xkbAccessX.c
xkbActions.c xkb: push locked modifier state down to attached slave devices 2014-03-11 17:43:34 +10:00
xkbDflts.h
xkbEvents.c
xkbInit.c
xkbLEDs.c
xkbPrKeyEv.c
xkbSwap.c
xkbUtils.c
xkbfmisc.c
xkbgeom.h
xkbout.c
xkbtext.c
xkmread.c

The X server uses this directory to store the compiled version of the
current keymap and/or any scratch keymaps used by clients.  The X server
or some other tool might destroy or replace the files in this directory,
so it is not a safe place to store compiled keymaps for long periods of
time.  The default keymap for any server is usually stored in:
     X<num>-default.xkm
where <num> is the display number of the server in question, which makes
it possible for several servers *on the same host* to share the same 
directory.

Unless the X server is modified, sharing this directory between servers on
different hosts could cause problems.