kc3-lang/libxkbcommon/src

• Show log

  Commit

• Hash : a1f0595a
  Author :
  Date : 2014-08-18T20:27:07
  

  state: make sure the mods are fully resolved after xkb_state_update_mask() Virtual modifiers can have "mappings" to real modifiers, e.g. NumLock may also set Mod2. In a normal turn of events, the various components (depressed, latched, locked, and consequently effective) include the mapped mods, because the masks are pre-resolved everywhere. However, xkb_state_update_mask() accepts arbitrary mod masks, which may not be resolved (if it comes from somewhere other than xkb_state_serialize_mods()). So let's always resolve them ourselves. Signed-off-by: Ran Benita <ran234@gmail.com>

• Files

• atom.c
• atom.h
• compat.c
• context-priv.c
• context.c
• context.h
• darray.h
• keymap-priv.c
• keymap.c
• keymap.h
• keysym-utf.c
• keysym.c
• keysym.h
• ks_tables.h
• scanner-utils.h
• state.c
• text.c
• text.h
• utf8.c
• utf8.h
• utils.c
• utils.h
• x11/
• xkbcomp/

• Properties

• Git HTTP	https://git.kmx.io/kc3-lang/libxkbcommon.git
  Git SSH	git@git.kmx.io:kc3-lang/libxkbcommon.git
  Public access ?	public
  Description
  Users
  Tags