Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!apple!uokmax!geohub.gcn.uoknor.edu!dwight
From: dwight@geohub.gcn.uoknor.edu (Dwight D. Moore)
Newsgroups: comp.windows.x.motif
Subject: RE: keystroke capture in Motif
Message-ID: <1991Feb11.104257@geohub.gcn.uoknor.edu>
Date: 11 Feb 91 16:47:10 GMT
References: <545@decvax.decvax.dec.com.UUCP> <1991Feb5.234055.8735@linus.mitre.org>
Sender: news@uokmax.ecn.uoknor.edu (Nets)
Reply-To: dwight@geohub.gcn.uoknor.edu
Distribution: na
Organization: Geosciences Computing Network, Univ. of Oklahoma
Lines: 37

I>In article <1991Feb5.234055.8735@linus.mitre.org>, lfs@mbunix.mitre.org
(Sheats) writes:
|>|> >Article 1661 in comp.windows.x.motif
|>|> >From: doc@xyvi.UUCP (Murtaza A. Doctor)
|>|> >I am attempting to capture keystrokes under a motif environment for
|>|> >performance evaluation. There does not appear to be any interface
|>|> >function available to do this.
|>|> > If any information about keystroke capture under motif is available
|>|> >I would greatly appreciate a response. Thank you.
|>|> 
|>|> I would also appreciate a response.  In addition, if the ability to
capture
|>|> keystrokes is available (either under Xlib, Xt or Xm), I would be
interested
|>|> in knowing whether or not the saved keystrokes can be "played back" (i.e.
can
|>|> the saved input be "fed" back to the server to put the application into
some
|>|> kind of "auto-pilot" mode)?
|>|> 
|>|> Any information on this subject would be greatly appreciated.
|>
|
You  could try looking into the XtAppAddActionHook() in the Xtoolkit.
This can register an Action routine to be called  when an action routine is
about to be
called .  The routine you register is called before the action routine. RTFM.

----------------------------------------------------------------------------
                                Dwight D. Moore
                         Geosciences Computing Network
                            University of Oklahoma

                  dwight@geohub.gcn.uoknor.edu (129.15.40.10)

Usual disclaimer.
----------------------------------------------------------------------------