MappingNotify Events

[Steven J Abner]

I'm receiving this signal and uncertain how to handle.

The application starts up on a bare x server. I do call, on start up, 
xcb_get_keyboard_mapping_reply() and xcb_get_keyboard_mapping_keysyms() 
to
read codes for responding to key events. The information from 
documentation says I get the event in response to 
XSetModifierMapping(), XChangeKeyboardMapping(), or 
XSetPointerMapping(). I'm guessing the xcb calls may be calling these? 
This is my debug output surrounding the event:

  /* Move */
window 4194309, CONFIGURE_NOTIFY. (100,102,500,500) _process_event
window 4194309, CONFIGURE_NOTIFY. (125,423,500,500) _process_event
window 4194309, BUTTON_RELEASE Button 1 modifier 256 (485,10) 
_process_event
window 4194309, BUTTON_RELEASE Button 1 modifier 256 (485,10) 
_default_headerbar_meter
  /* Redraw Button (move indicator) */
window 4194309, EXPOSE. Region (477,5,14,14) _process_event
Unknown event: 34 _process_event
Unknown event: 34
Unknown event: 34 _process_event
Unknown event: 34
  /* Switch to be a resize event */
window 4194309, KEY_PRESS. code 37 modifers 0 keyval ffe3 key_name 
XK_Control_L _process_event
window 4194309, KEY_PRESS. code 37 modifers 0 keyval ffe3 key_name 
XK_Control_L _default_headerbar_meter
window 4194309, KEY_PRESS. code 37 modifers 0 keyval ffe3 key_name 
XK_Control_L _default_interface_meter
window 4194309, KEY_PRESS. code 37 modifers 0 keyval ffe3 key_name 
XK_Control_L _default_headerbar_meter
  /* Redraw Button (resize indicator) */
window 4194309, EXPOSE. Region (477,5,14,14) _process_event

Note: this code as far as server time a ways from original keysym calls.
I include this because I don't know if I'm screwing up.

According to documentation, I'm to respond by the xcb equivalent to 
XRefreshKeyboardMapping(). I'm uncertain if I need to update my pointer 
to keysyms, recheck stride and min? I'm unaware of me changing 
anything. If I do respond with XRefreshKeyboardMapping() then do I need 
to update my pointer/stride/min? Nothing on my limited testing ever 
showed an issue, but maybe a window manager addressed this, or with no 
manager the Xterm console addressed this prior to start of application?

Sorry if info on event lacking, but I don't know what I'm looking at or 
for.
Steve