Hi Michael,
I have seen similar problem on my new HP Windows. But I used Xming
package (Cygwin) instead of Exceed. The problem, as Mark pointed out, was
the XKEYSYMDB setting. I pointed it to the file in "EPICS Win32 Extension"
directory, which somehow didn't work for my new PC. I found a newer version
of XKEYSYMDB in Xming (Cygwin) directory, which dated 2005 vs. 2000 for the
one in EPICS directory, and it worked.
Zhan
----------------------------------
Zhan Zhang, Ph.D
Argonne National Laboratory
X-ray Science Division, Bldg 438, D005
9700 S. Cass Ave.
Argonne, IL 60439
Tel: (630) 252-0863
Email: [email protected]
> -----Original Message-----
> From: Mark Rivers [mailto:[email protected]]
> Sent: Friday, January 26, 2007 10:32 PM
> To: Michael Urashka; [email protected]
> Subject: RE: MEDM behavior, can't type in text edit box.
>
>
> Hi Michael,
>
> I have heard reports of this on other X servers.
>
> This is from the Win32 EPICS Extensions Readme.txt file:
>
> *****
> Note that the build Exceed version changed from 6.2 to 7.0
> with Build 32 and the behavior of Exceed 7 is different from
> that of 6.2. If you are upgrading from a build prior to Build
> 32, you should review the instructions as the installation
> has changed. If your version of Exceed is different from the
> build version, especially if it is prior to Exceed 6.1, you
> may need to set the environment variable DISPLAY, possibly
> XKEYSYMDB, and possibly XLOCALEDIR.
> *****
>
> I suspect the problem is that you need to define XKEYSYMDB?
> Here is how to do it from the same Readme.txt file:
>
> *****
> Setting XKEYSYMDB causes Exceed to find the Keysym database
> in the EPICS WIN32 Extensions directory. The Exceed support
> files do not need to be installed. If you have Exceed 5,
> this will always be necessary. It may also be necessary if
> you have another earlier version, unless you have the Exceed
> XDK. It will also probably be necessary if you are not using
> Exceed. If you are getting messages about unfound keysyms,
> such as osfActivate, set this variable. If the EPICS WIN32
> Extensions are in the default location, the command is:
>
> set XKEYSYMDB=c:\Program Files\EPICS WIN32 Extensions\XKeySymDB
> *****
>
> Mark
>
>
>
> ________________________________
>
> From: Michael Urashka [mailto:[email protected]]
> Sent: Fri 1/26/2007 7:34 PM
> To: [email protected]
> Subject: MEDM behavior, can't type in text edit box.
>
>
>
> Has any seen this behavior before (or have a suggestion as to
> what is going on).
>
> MEDM is installed as per the Windows Win32 EPICS Extension
> package along with Hummingbird Exceed 10.
>
> On several of the Control Room consoles, MEDM behaves
> normally, as it does on my development desktop.
>
> On another bunch of the Control Room consoles, MEDM launches
> fine but will not take keyboard input. One is able to mouse
> onto a new canvas and create a new object widget, a Textt
> Monitor for example. When one clicks on the "Text" field (or
> the "Channel A", "Channel B", "Width", "Height" fields) in
> the Resource Palette, one is not able to make any entries
> with the keyboard.
>
> I am certain I am using the correct keyboard plugged into the
> correct PCs and that the keyboards function normally in other
> applications.
>
> Any suggestions?
>
>
> --
> Michael Urashka | Advanced Light Source
>
>
>
- References:
- RE: MEDM behavior, can't type in text edit box. Mark Rivers
- Navigate by Date:
- Prev:
EPICS and HEPiX Rees, NP (Nick)
- Next:
StreamDevice and checksum Phillip Sorensen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: MEDM behavior, can't type in text edit box. Mark Rivers
- Next:
EPICS and HEPiX Rees, NP (Nick)
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|