- start assigning custom VK codes from VK_OEM_8 since this code
commit11af61652b0e410408aa269117b7454eb1b52bca
authorDmitry Timoshkov <dmitry@codeweavers.com>
Sat, 17 Apr 2004 00:21:51 +0000 (17 00:21 +0000)
committerAlexandre Julliard <julliard@winehq.org>
Sat, 17 Apr 2004 00:21:51 +0000 (17 00:21 +0000)
tree15d6352f2b93a9f0c2835a041dfbccc2a066fa8b
parent8183eb658fef644e73afa7d3dd6f4477c1e355e9
- start assigning custom VK codes from VK_OEM_8 since this code
  already presents in the layout tables
- search the layout tables only if XLookupString returned non zero
  number of characters for a keysym, otherwise that's a non character
  key
- avoid inserting VK_OEM_x codes into unassigned positions since these
  codes might already be in the layout table, thus creating a conflict
dlls/x11drv/keyboard.c