Rick,
My guess is this happens because you don't have that key in your map.
I just saw these messages (with your new code) :
dell: {25} oleo
Warning:
Name: editmenu
Class: XmRowColumn
Manager.c:_XmManagerInstallAccelerator(2088) - Could not convert
>Ctrl<Key>osfInsert< to a KeyCode
Ctrl<Key>osfInsert -> 1004ff63 -> 0
Warning:
Name: editmenu
Class: XmRowColumn
Manager.c:_XmManagerInstallAccelerator(2088) - Could not convert
>Ctrl<Key>osfInsert< to a KeyCode
Ctrl<Key>osfInsert -> 1004ff63 -> 0
When I ran "xmodmap -pk | grep osfInsert" that key didn't
appear. Note that osfInsert is my problem area, you mention
osfEndLine. Would you have a key linked to osfInsert but no key
that means osfEndLine ?
In any case I'd vote for making this silent - we'll have too many
strange messags coming out of LessTif this way. Can you fix before the
release (if you agree) ?
Danny
Rick Scott wrote:
>
> Who can tell me something about Motif virtual keys, and all this keyboard
> handling stuff in general. openDX is installing an accelerator of
> Ctrl<Key>osfEndLine, which we turn into the KeySym 0x1004ff57. Now
> XKeysymToKeycode takes this and returns 0 for the KeyCode. This means that it
> couldn't convert it, but we don't care and slap a grab on it anyway. The
> problem is that 0 just so happens to be AnyKey to the XtGrabKey routine. Which
> means we end up grabbing the entire keyboard as an accelerator!!!!
>
> 10 points goes to anyone who can figure out why we can't convert osfEndLine
> into a valid KeyCode.....
>
> I think I'm also going to add in the check for an XKeysymToKeycode failure
> during the freeze period. It's pretty obvious that we shouldn't be adding a
> grab for a keycode that results from a failed conversion.
>
> If someone really objects, back it out.......
--
Danny Backx ([EMAIL PROTECTED] [EMAIL PROTECTED])
Home page : http://users.skynet.be/danny.backx
Projects: LessTif (http://www.lesstif.org)
Oleo (http://www.gnu.org/software/oleo/oleo.html)
