High priority? Should we refine keyboard support? I notice that DynAPI2 has
some rather unsupported and incomplete functionality for keyevents. I was
checking the posting of patches and found Henrik Våglin's keys.js (not the
one found in ext already), it refines keyboard support, shouldn't it be
placed in the API? BTW, I noticed that it also suffers from the same
problems that keyevents.js has in the ext package. Keycodes for IE need to
be remapped. I've included an attatchment that corrects for the incorrect
key codes for IE; my version of keys.js. it includes corrections for
punctuation, case, and other special keys. I don't write the most optimized
code, so perhaps someone could look take a look at it first? I functions
well. Also, I've fixed NS shift and cntrl key values to be booleans, this is
so that both IE and Netscape behave the same way (as it should be) when
using my version of keys.js for keyboard support (got tired of compensating
within my widgets).
PS. I've made a killer textbox widget, including a blinking cursor, but I
can't pick up the keycodes for arror keys in Netscape 4.7, I guess there is
no way around that one...
Best regards,
Steve
key.zip
