Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!tank!eecae!cps3xx!cpsvax!dulimart From: dulimart@cpsvax.cps.msu.edu (Hansye S. Dulimarta) Newsgroups: comp.windows.x Subject: Re: Changing label Message-ID: <4344@cps3xx.UUCP> Date: 28 Aug 89 20:11:54 GMT References: <4337@cps3xx.UUCP> <8908281827.AA07142@expo.lcs.mit.edu> Sender: usenet@cps3xx.UUCP Reply-To: dulimart@cpsvax.UUCP (Hansye S. Dulimarta) Organization: Michigan State University, Computer Science Department Lines: 33 In article <8908281827.AA07142@expo.lcs.mit.edu> kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) writes: > >> My problem is : I didn't get message #1 thru #(n-1) on my window, >> but only the LAST message (#n). > >The X toolkit only processes events in XtMainLoop. Even though you have asked >the label widget to display a new string the event is not sent to the server >until you get into XtMainLoop. A quick fix to the problem is to put an >XFlush() call into your client after the XtSetValues() call. This will flush >the request to the server immediately. > >NOTE: This method assumes that your label widget is mapped and viewable before > you enter the callback proc. If you want to pop up the message label > then things get more complicated. > > Chris D. Peterson > MIT X Consortium I think XFlush() must be treated differently from other requests (doesn't have to go the the buffer), because if it does then how can it flush the buffer ? I tried to add XFlush() after XtSetValues() to my Message procedure, but it remains the SAME. Only the last message I saw on the window. Any other suggestion ? /*---------------------------------------------------------------------------* * Hans Dulimarta (517) 355-3840 * * dulimart@cpsvax.cps.msu.edu * * {....}!tank!eecae!cpsvax!dulimart * * 35.8.56.111 * * * * "Fear of the LORD is the beginning of knowledge" Proverb 1:7 * *---------------------------------------------------------------------------*/