nanogui@linuxhacker.org

Greg & List,

Okay, I'm in the middle of extending keyboard support for
microwindows.  Presently microwindows only delivers full characters,
and only of type ascii's... this is going to change.  What I need from
you guys are comments on how you think this should be done.  Presently
it sets the modifier bit's to one of the following:
GR_MODIFIER_ALT
GR_MODIFIER_SHIFT
GR_MODIFIER_META (Ctrl key, BTW)
GR_NON_ASCII

Under condition "non ascii" it loads up non ascii symbols from
within microwindows..., i.e. MW_HOME, MW_PGUP, MW_PGDOWN, etc.  What
I'm thinking is that that's sort of "hacky" and we should probably go
to a fully abstracted interface.  I.e. kill the ascii stuff, and just
do our own implementations for everything.  (This is already being
done for the Windows API)

Also I'm working on support for both KeyPress events, and KeyRelease
events.  In it's present incarnation these will not be active for
ascii associated keys, only non ascii associated ones.  (Inline with
the way the Win32 functions... sort of)  The "shift-a's" are already
mapping to A's, so that's all fixed up.  Also no characters are being
printed for <Ctrl>, <Pgup>, etc. etc.

So... should we stick with this hacked up ascii/internal format, or
fully abstract?  If fully abstract I'm leaning towards just
"borrowing" all the mappings from X. (<X11/symkeydefs.h>, I think...)

Now I have the great majority of this extended keyboard support
working for the running within X11 version of Microwindows, but I will
need some help from someone more familiar with the other keyboard
mapping files.  (i.e. the bios, djgr, pac and tc files)  Just if
someone could drop me the info on how they map their keyboards would
be fine, I have no problem implementing it, it's just a matter of
filling in blanks in my keyboard memory file :>.  (Or just some source
would be fine too)

Alright... thanks everyone,
Shane.