Apache/2.4.7 (Ubuntu) Linux sman1baleendah 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 uid=33(www-data) gid=33(www-data) groups=33(www-data) safemode : OFF MySQL: ON | Perl: ON | cURL: OFF | WGet: ON > / usr / share / X11 / xkb / compat / | server ip : 172.67.156.115 your ip : 172.69.130.155 H O M E |
Filename | /usr/share/X11/xkb/compat/xtest |
Size | 1.44 kb |
Permission | rw-r--r-- |
Owner | root : root |
Create time | 27-Apr-2025 09:50 |
Last modified | 15-Jan-2014 22:42 |
Last accessed | 07-Jul-2025 00:13 |
Actions | edit | rename | delete | download (gzip) |
View | text | code | image |
default xkb_compatibility "xtest" {
// Minimal set of symbol interpretations to provide
// reasonable behavior for testing. The X Test
// Suite assumes that it can set any modifier by
// simulating a KeyPress and clear it by simulating
// a KeyRelease. Because of the way that XKB
// implements locking/latching modifiers, this
// approach fails in some cases (typically the
// lock or num lock modifiers). These symbol
// interpretations make all modifier keys just
// set the corresponding modifier so that xtest
// will see the behavior it expects.
virtual_modifiers NumLock,AltGr;
interpret.repeat= False;
setMods.clearLocks= True;
latchMods.clearLocks= True;
latchMods.latchToLock= False;
interpret Shift_Lock+AnyOf(Shift+Lock) {
action= SetMods(modifiers=Shift);
};
interpret Num_Lock+Any {
virtualModifier= NumLock;
action= SetMods(modifiers=NumLock);
};
interpret Mode_switch {
useModMapMods= level1;
virtualModifier= AltGr;
action= SetGroup(group=2);
};
interpret Any + Any {
action= SetMods(modifiers=modMapMods);
};
group 2 = AltGr;
group 3 = AltGr;
group 4 = AltGr;
indicator.allowExplicit= False;
indicator "Caps Lock" {
modifiers= Lock;
};
indicator "Num Lock" {
modifiers= NumLock;
};
indicator "Shift Lock" {
whichModState= Locked;
modifiers= Shift;
};
indicator.allowExplicit= True;
};
// Minimal set of symbol interpretations to provide
// reasonable behavior for testing. The X Test
// Suite assumes that it can set any modifier by
// simulating a KeyPress and clear it by simulating
// a KeyRelease. Because of the way that XKB
// implements locking/latching modifiers, this
// approach fails in some cases (typically the
// lock or num lock modifiers). These symbol
// interpretations make all modifier keys just
// set the corresponding modifier so that xtest
// will see the behavior it expects.
virtual_modifiers NumLock,AltGr;
interpret.repeat= False;
setMods.clearLocks= True;
latchMods.clearLocks= True;
latchMods.latchToLock= False;
interpret Shift_Lock+AnyOf(Shift+Lock) {
action= SetMods(modifiers=Shift);
};
interpret Num_Lock+Any {
virtualModifier= NumLock;
action= SetMods(modifiers=NumLock);
};
interpret Mode_switch {
useModMapMods= level1;
virtualModifier= AltGr;
action= SetGroup(group=2);
};
interpret Any + Any {
action= SetMods(modifiers=modMapMods);
};
group 2 = AltGr;
group 3 = AltGr;
group 4 = AltGr;
indicator.allowExplicit= False;
indicator "Caps Lock" {
modifiers= Lock;
};
indicator "Num Lock" {
modifiers= NumLock;
};
indicator "Shift Lock" {
whichModState= Locked;
modifiers= Shift;
};
indicator.allowExplicit= True;
};