Simple enough

I made a loadable which executes a load module for xchars, then a New Conn and New Window, then enters message loop. The messages include key press and ascii equivalents, chars!

But it demonstrates the ability of one loadable to load another while being initialized, so we can cascade the loadables by dependency. Universal interface, symbol table up front of xchars make it simple.
I cannot keyscan mapping xcb.  Evidently converting from keyboard scan values to ascii is not so simple as all the keyboard makes use different scan code, and xcb is in flux about that.

The implication is that I have to use X11, but X11 wants a display, not a connection though they call it a connection. I dunno what a display is, the piece of hardware sitting in front of me?  The xcb folks have a simple solution but it requires something called xcb utils, and no one seems to think it is deployed yet.  This is a problem to be has been solved, somehow.

Solution to the keyscan code problem.

Wait a day r two and keep looking around. Someone has built a scan code converter and package called xkbcommon, but I have a hard time understanding how a two step look up results in 20 different files.  X11 can get you to a symbol, but Morse Code is more valuable to me than a symbol string, with Mores Code i can convert to ascii in one step.  How did x11 ever firue out to take a byte or two and convert it into a string?  Why not go through the map table, convert is to ascii, baudot, or morse code?.  How does it help any one to have a sting called:

I can use X121 key scan conversion, a two step process.  I have discovered where my screen is, so I should be able to make the call.

This part still confuses.  The issue s converting from one integer through another, I am not sure why X11 ever go something called a screen involved. It is the keyboard that matters, if you are ghoing to look up key strokes the correct call is:
XLL_keyySim(mykeyborad, code);

The idea is to not confuse anyone by connecting a table look up with a bitmap, two separate things.  In fact, I have a hard time understanding what any of this keyboard crap has to to with X11, the key strokes and the bit map and entirely separate, who the frig connected them? Oh, yes, the bricklayers at MIT.