Sebastian Reuße <s...@wirrsal.net> writes: > XkbGetMap is more robust in cases where certain keyboard description > components > are missing. XkbGetKeyboard will fail when any component cannot be resolved; > since all XkbAllComponentsMask is requested, any missing component will result > in the call returning NULL. Since we don’t necessarily need all > components (e.g., keyboard geometry, keymap names), we use XkbGetMap instead.
Alternatively, one might try whether a less encompassing components mask will do. XkbGetMap appears to just NULL those components of the struct which are unavailable, while XkbGetKeyboard will return NULL wholesale. Best regards, SR -- Insane cobra split the wood Trader of the lowland breed Call a jittney, drive away In the slipstream we will stay ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
