Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!deccrl!bloom-beacon!dont-send-mail-to-path-lines
From: swick@athena.mit.EDU (Ralph Swick)
Newsgroups: comp.windows.x
Subject: Re: ProcessContext in X11R4 Xt library (bug?).
Message-ID: <9105091345.AA07650@lyre.MIT.EDU>
Date: 9 May 91 13:45:40 GMT
References: <MATT.91May9141022@henry.bacchus.esa.oz>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 28


    The symptom was that a home-grown widget's translation
    table was being 'handled' OK but the action table for it was being
    ignored - result: 'Warning: Actions not found:' error messages.

Is your application (or the home-grown widget) still using XtAddActions
rather than XtAppAddActions?  (There's no good reason I can think of
for the widget to be registering actions this way, but it's a thought.)

The "default application context" is useful only for the compatibility
routines in Appendix C of the Xt spec.  If you use XtAppInitialize, as
you should, then you must not use any of the appendix C routines in the
following right-hand column:

	New			  Replaces

	XtAppMainLoop		  XtMainLoop
	XtAppNextEvent		  XtNextEvent
	XtAppProcessEvent	  XtProcessEvent
	XtAppPeekEvent		  XtPeekEvent
	XtAppPending		  XtPending
	XtAppAddInput		  XtAddInput
	XtAppAddTimeOut		  XtAddTimeOut
	XtAppAddWorkProc	  XtAddWorkProc
	XtAppCreateShell	  XtCreateApplicationShell
	XtAppAddActions		  XtAddActions
	XtAppSetSelectionTimeout  XtSetSelectionTimeout
	XtAppGetSelectionTimeout  XtGetSelectionTimeout