On Mon, Jun 16 2025 at 11:14:01 AM +0000, Steven J Abner
<[email protected]> wrote:
I include this because I don't know if I'm screwing up.
It appears that I don't know the pre/post-function, or bit, to set
keyboard has been accessed prior to or after I make calls to cached the
keyboard data.
Sorry if info on event lacking, but I don't know what I'm looking at
or for.
More info:
The mapping event only occurs on non-WM. Exception being if it's a
spawned process of Xterm with/without going thru gdb. I assume WM just
block or ignore?
Three different apps running simultaneously, each with three tests to
validate keymap, were at startup (caching), and the 2 mapping notify
events:
MAPPING. min_keycode=8 max_keycode=255 keysyms=0x559a7602d6c0
window 0, MAPPING_NOTIFY. request=1 first=8 count=248 _process_event
window 0, MAPPING_NOTIFY. request=0 first=0 count=0 _process_event
All 3 at 3 events identical except the pointer to keysyms for each app.
So the question becomes:
What are/is the pre/post-function(s), or bit to call/set for using
xcb_get_keyboard_mapping_reply() and xcb_get_keyboard_mapping_keysyms()?
Or is it obvious that prior to run loop I create a XMappingEvent to
send with XRefreshKeyboardMapping(), with flush?
Steve
