These are MOTIF keyboard mapping issues and XKeysymDB file provides it. It has really nothing to do with OpenDX code or version. You need to check Hummigbird Tech Support and their knowledge Base at their URL.
Suhaib > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 12, 2001 12:51 PM > To: [email protected] > Subject: RE: Re: [opendx-users] Opendx for windows/nt > > > I am using Exceed 5.1.3 and it worked fine with DX 4.1.1. > > > > > > Suhaib Siddiqi > <[EMAIL PROTECTED]> To: > "'[email protected]'" > Sent by: <opendx- > [EMAIL PROTECTED]> > [EMAIL PROTECTED] cc: > on.ibm.com Subject: > RE: Re: [opendx-users] Opendx for windows/nt > > > 07/12/01 11:37 AM > Please respond to opendx-users > > > > > > Which Xserver? Setting XkeysymDB should fix it. If it does not > then there > is something wrong with your XkeysymDB file and you should contact > the > vendor of your X-server for technical support. > > Suhaib > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Sent: Thursday, July 12, 2001 11:54 AM > > To: [email protected] > > Subject: RE: Re: [opendx-users] Opendx for windows/nt > > > > > > I have had the same problem with the keyboard as described > below. > > I have > > tried to implement the solution also described at it has not > > worked. > > > > Here is an example of the several warning messages I see in the > > MSDOS > > window when I start DX. > > > > > > > > XtWarning: ... found while parsing ':<Key>osfUp: > > MenuTraverseUp() > > ' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfDown > > XtWarning: ... found while parsing ':<Key>osfDown: > > MenuTraverseDown > > ()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfSelect > > XtWarning: ... found while parsing ':<Key>osfSelect: > > ArmAndActivate()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfActivate > > XtWarning: ... found while parsing ':<Key>osfActivate: > > ArmAndActivate()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfCancel > > XtWarning: ... found while parsing ':<Key>osfCancel: > > MenuEscape()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfHelp > > XtWarning: ... found while parsing ':<Key>osfHelp: > > Help()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfActivate > > XtWarning: ... found while parsing ':<Key>osfActivate: > > PrimitiveParentA > > ctivate()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfCancel > > XtWarning: ... found while parsing ':<Key>osfCancel: > > PrimitiveParentC > > ancel()' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfSelect > > XtWarning: ... found while parsing ':<Key>osfSelect: > > ArmAndActivate() > > ' > > XtWarning: translation table syntax error: Unknown keysym name: > > osfHelp > > XtWarning: ... found while parsing ':<Key>osfHelp: > > Help()' > > > > > > > > > > > > > > > > > > > > Gib Bogle <[EMAIL PROTECTED]> > > Sent by: To: > > "'[email protected]'" > > [EMAIL PROTECTED] > <opendx- > > [EMAIL PROTECTED]> > > on.ibm.com cc: > > > Subject: > > RE: Re: [opendx-users] Opendx for windows/nt > > > > 07/08/01 04:42 PM > > Please respond to opendx-users > > > > > > > > > > > > > -----Original Message----- > > > From: Allard [mailto:[EMAIL PROTECTED] > > > Sent: Sunday, 8 July 2001 03:48 > > > To: [email protected] > > > Subject: Re: Re: [opendx-users] Opendx for windows/nt > > > > > > > > > I have seen this too when I tried to run the windbarbs.net > > > example program. > > > > > > Also, I have experienced the problem with the sequencer which > > > others have > > > been experiencing when I try to configure the range of the > > > frames that I > > > wish to view. When I keep the defaults (1-100), it works > fine. > > > > There are problems with Ver 4.1.3, which is why I have gone back > > to using > > Ver 4.1.1. No doubt this will be sorted out soon. > > > > > I have also been getting errors relating to the keyboard. > > > For example, if I > > > try to highlight a directory name in the file browser and then > > hit > > > "backspace" to erase the name so I can put my directory in, > the > > cursor > > > advances as if I hit the space bar. I get the same result > when > > I hit > > > "delete". Also, "delete" won't work in the program editor > > > window to cut a > > > module. I have to go to the menu and use the mouse. > > > > > > > This is a separate issue, easily solved. You need to tell > Exceed > > (or is it > > OpenDX?) where to find the file XkeysymDB (you first need to > find > > this > > file, > > which the Exceed installation will have put somewhere). The > > easiest way is > > to create an environment variable equal to the file path, e.g.: > > > > Set XkeysymDB=c:\Windows\Application > > Data\Hummingbird\Connectivity\7.00\Exceed\XkeysymDB > > > > I put this in the batch file that I always run first when > starting > > OpenDX. > > > > Gib > > > > NOTICE - This e-mail is only intended to be read by the named > > recipient. > > It > > may contain information which is confidential, proprietary or > the > > subject > > of > > legal privilege. If you are not the intended recipient please > > notify the > > sender immediately and delete this e-mail. You may not use any > > information > > contained in it. Legal privilege is not waived because you have > > read this > > e-mail. > > > > For further information on the Beca Group of Companies, visit > our > > web page > > http://www.beca.co.nz > > > > > > >
