[twobob]

okay. doing some digging. anything above 255 seems to just "wrap-around".
(which makes sense)

CAPS LOCK is 66. (it would seem)

Here's what I was testing with

all the codes marked here CLOSE the keyboard in some way. The others either make no chars, are control codes, or a printable char.

export MOD=255; while [ ! "${MOD}" = "8" ]; do export MOD=`expr ${MOD} - 1`; if [ ! "${MOD}" = "66" ] && [ ! "${MOD}" = "110" ] && [ ! "${MOD}" = "36" ] && [ !
"${MOD}" = "78" ] && [ ! "${MOD}" = "70" ] && [ ! "${MOD}" = "69" ] && [ ! "${MOD}" = "68" ] && [ ! "${MOD}" = "67" ] && [ ! "${MOD}" = "110" ] && [ ! "${MOD}" = "104" ] then eips "${MOD} ."; usleep 90000; echo ${MOD}; xsendkeycode $MOD 1; xsendkeycode $MOD 0; fi; usleep 90000; do
ne;


So 66 is Caps Lock (I believe)
110, 36, 78, 70, 69, 68, 67, 104 are other keyboard-closing key codes

There is no "upper and lower" register set.

Will have to figure out what maps to what at some point. did most of em.

No single character code generates the "Double characters" you are experiencing, thus it has to be the "Shift"code we are passing is wrong.

Bit more derping should probably nail it.

There are many more in the upper registers that I missed like YEN ¥ Pound £ and _ & ^ | et cetera...

Interestingly: RIGHT SHIFT maps to the weird 90 degrees pipe character and left maps to £ which explains the symbols preceding your keystrokes.

Far as I can make out uppercase expects a Caps Lock 66 then the key on/off then the release. As opposed to a standard shift.

I know very little about this stuff but hope all this work helps someone who DOES know what they are talking about a bit of time.

I think mapping the leftover CTRL keys is probably a worthwhile exercise, for someone.

I'm way bored of this now.