Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!asente
From: asente@decwrl.dec.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: Xt Problem [XtDispatchEvent()]
Message-ID: <1108@bacchus.dec.com>
Date: 19 Feb 89 22:20:08 GMT
References: <1093@bacchus.dec.com> <8902182246.AA08494@special-k.ai.mit.edu>
Organization: DEC Western Software Lab
Lines: 23

In article <8902182246.AA08494@special-k.ai.mit.edu> sundar@WHEATIES.AI.MIT.EDU (Sundar Narasimhan) writes:
>Thanks for that explanation. I've always wondered why my recursive calls to
>XtDispatchEvent were so slow sometimes. (I am still annoyed by
>the unpredictability of the time it takes -- there should be a faster
>way to do this if I can guarantee that I wont have any calls that
>destroy widgets in my recursive call to DispatchEvent, no?)
>
>-Sundar

Well, if you don't have any destroys to execute, all that's happening is a
few assignments and a check if the destroy list is NULL.  If your
dispatches are taking longer sometimes, and you aren't destroying
anything, it's coming from someplace else -- possibly large translation
tables, or the keyboard focus mechanism's cache failing (keyboard events
usually come in for the same widget they just came in for, so the
intrinsics can cache the focus widget and use that unless the set of
keyboard focus directives has changed or the event comes in for a
different widget).

Hope this helps...

	-paul asente
	    asente@decwrl.dec.com	decwrl!asente